What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

WAN DNS setting ignored due to pppd - 386.13 on Asus AC68u

R3dbvll

New Around Here
Hi all,

I'm really hoping someone can help.
I have an Asus AC68u router (which I realise is old and now no longer supported), but it is still going strong. Currently I'm running Merlin firmware 386.13 on it.

I have just moved house and moved ISPs. Previously I was with Virgin Media, who provided a DOCSIS service. I was able to set the WAN-side DNS servers I wanted to use for the router with no problem - I set this in the router UI.

The new ISP uses PPPoE. I have a Draytek Vigor167 modem in bridge mode fronting the connection, then the Asus router. Everything works fine except for the WAN DNS settings.

From what I can tell in the logs, pppd is pulling the the ISP provided DNS servers and pushing them to file, which dnsmasq is then picking up. Nothing I do seems to change that.
I've tried adding the config option 'ms-dns' in the Additional PPPD Options field, but it makes no difference.

Are there any other pppd options I can provide, or are there other options available to make sure dnsmasq picks up my desired DNS servers?

(note, if interested - the LAN-side DNS settings work fine, and are provided by DHCP to LAN clients)

I checked through the release notes of new firmware versions, but I didn't see anything that could be related.

Many thanks
Chris.
 
I ran a RT-AC68U for many years with my PPPoE ISP and never had this issue.

I would recommend upgrading to the final 386.14_2 then doing a factory reset.

Also trying DoT set to strict + DNSSC, as that was my config.
 
Please show what your WAN DNS settings look like and the syslog snippet that shows the ISP DNS servers being read.
 
Currently I'm running Merlin firmware 386.13 on it.
The firmware 386.13 (7-Apr-2024) is almost a year old. You really should update to the latest 386.14_2 (17-Nov-2024) firmware if for nothing other than the security vulnerability fix(es) it contains, namely the one for the AiCloud vulnerability:

Retest and see if your issue persists with the latest firmware.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top