Custom WAN DNS not working

[Gary_Dexter]

No but you could overwrite nvram entries and see if it sticks.

nvram set wan_dns="9.9.9.9 149.112.112.112"
nvram set wan0_dns="9.9.9.9 149.112.112.112"
nvram commit

Then reboot when you can.

Just tried this. And sadly no difference.

 

[dave14305]

Just tried this. And sadly no difference.

That‘s nuts. How about:

nvram show | grep -F "212.23.3"
nvram show | grep -E "^wan.*dns"

 

[Gary_Dexter]

That‘s nuts. How about:

nvram show | grep -F "212.23.3"
nvram show | grep -E "^wan.*dns"

nvram show | grep -F "212.23.3"
wan0_dns=212.23.3.100 212.23.6.100
size: 73921 bytes (57151 left)

—

nvram show | grep -E "^wan.*dns"
wan0_dns=212.23.3.100 212.23.6.100
wan0_dns1_x=9.9.9.9
wan0_dns2_x=149.112.112.112
wan0_dnsenable_x=0
wan0_xdns=9.9.9.9 149.112.112.112
wan1_dns=
wan1_dns1_x=
wan1_dns2_x=
size: 73921 bytes (57151 left)
wan1_dnsenable_x=1
wan_dns=9.9.9.9 149.112.112.112
wan_dns1_x=9.9.9.9
wan_dns2_x=149.112.112.112
wan_dnsenable_x=0

 

[dave14305]

Time for an exorcist…

 

[Gary_Dexter]

Time for an exorcist…

Agreed. It can wait til the weekend

 

[dave14305]

Agreed. It can wait til the weekend

Try one more thing.

nvram set wan1_dnsenable_x=0
nvram commit
nvram show | grep -E "^wan.*primary"

Then reboot. A DHCP renew should not be overwriting your DNS settings.

 

[ColinTaylor]

wan0_xdns shouldn't exist AFAIK. It could be an nvram caching issue so try doing an nvram commit and running the command again. If it's still there try this:

nvram unset wan0_xdns
nvram commit

That said, it shouldn't really make any difference but it might be indicative of the actual problem.

 

[dave14305]

wan0_xdns shouldn't exist AFAIK. It could be an nvram caching issue so try doing an nvram commit and running the command again. If it's still there try this:

nvram unset wan0_xdns
nvram commit

That said, it shouldn't really make any difference but it might be indicative of the actual problem.

I think you can still have xdns with pppoe, pptp, or l2tp connections.

Do you use either of those Gary?

 

[Gary_Dexter]

I think you can still have xdns with pppoe, pptp, or l2tp connections.

Do you use either of those Gary?

PPPOE

 

[dave14305]

PPPOE

nvram show | grep -E "^wan.*(dns|primary|ifname)"

Please and thank you.

 

[Gary_Dexter]

nvram show | grep -E "^wan.*(dns|primary|ifname)"

Please and thank you.

nvram show | grep -E "^wan.*(dns
|primary|ifname)"
wan0_dns=212.23.3.100 212.23.6.100
wan0_dns1_x=9.9.9.9
wan0_dns2_x=149.112.112.112
wan0_dnsenable_x=0
wan0_gw_ifname=ppp0
wan0_ifname=vlan911
size: 73938 bytes (57134 left)
wan0_pppoe_ifname=ppp0
wan0_primary=1
wan0_xdns=9.9.9.9 149.112.112.112
wan1_dns=
wan1_dns1_x=
wan1_dns2_x=
wan1_dnsenable_x=1
wan1_ifname=
wan1_pppoe_ifname=
wan1_primary=0
wan_dns=212.23.3.100 212.23.6.100
wan_dns1_x=9.9.9.9
wan_dns2_x=149.112.112.112
wan_dnsenable_x=0
wan_ifname=eth0
wan_ifnames=vlan911

 

[dave14305]

nvram show | grep -E "^wan.*(dns
|primary|ifname)"
wan0_dns=212.23.3.100 212.23.6.100
wan0_dns1_x=9.9.9.9
wan0_dns2_x=149.112.112.112
wan0_dnsenable_x=0
wan0_gw_ifname=ppp0
wan0_ifname=vlan911
size: 73938 bytes (57134 left)
wan0_pppoe_ifname=ppp0
wan0_primary=1
wan0_xdns=9.9.9.9 149.112.112.112
wan1_dns=
wan1_dns1_x=
wan1_dns2_x=
wan1_dnsenable_x=1
wan1_ifname=
wan1_pppoe_ifname=
wan1_primary=0
wan_dns=212.23.3.100 212.23.6.100
wan_dns1_x=9.9.9.9
wan_dns2_x=149.112.112.112
wan_dnsenable_x=0
wan_ifname=eth0
wan_ifnames=vlan911

I’m ready to say it’s a flaw or feature of ppp.c. It unconditionally sets the dns value even if you want to specify your own. I’m not certain the code I link here gets called in your situation, but it seems to match what you’re showing.

asuswrt-merlin.ng/release/src/router/rc/ppp.c at ea1e2fbf24501f4bbe5c5a79c1232558e01802aa · RMerl/asuswrt-merlin.ng

Third party firmware for Asus routers (newer codebase) - RMerl/asuswrt-merlin.ng

github.com

 

[Gary_Dexter]

I’m ready to say it’s a flaw or feature of ppp.c. It unconditionally sets the dns value even if you want to specify your own. I’m not certain the code I link here gets called in your situation, but it seems to match what you’re showing.

asuswrt-merlin.ng/release/src/router/rc/ppp.c at ea1e2fbf24501f4bbe5c5a79c1232558e01802aa · RMerl/asuswrt-merlin.ng

Third party firmware for Asus routers (newer codebase) - RMerl/asuswrt-merlin.ng

github.com

OK.

So where from here?

Run some more commands? Factory reset? Or just accept that’s the way it works?

 

[dave14305]

OK.

So where from here?

Run some more commands? Factory reset? Or just accept that’s the way it works?

As time allows:

1. Reset to factory defaults and try again.
2. Install stock and reset to defaults and try again.
3. If 2, then report to Asus via Feedback form.

 

[Gary_Dexter]

As time allows:

1. Reset to factory defaults and try again.
2. Install stock and reset to defaults and try again.
3. If 2, then report to Asus via Feedback form.

Roger that. Weekend project

 

[glens]

Before that, how about setting everything which contains "enable" to "1"