manual DNS not working

[gamewarden3006]

Using Merlin build 354.28 beta 1

In the past I would use custom DNS servers (open dns, google dns ...)

simple just go to the WAN tab, click no to auto connect to DNS then enter the IP. I would occasionally change between manual ones and allowing it to auto connect to my internet providers automatically.

Well I have been running on auto for a while and wanted to change to a custom one so I changed it but could not browse internet. tried two or three different servers and still same result... am I missing something here??
Seems like I remember having to change something under the LAN tab at one point too.... been a while though...

Any suggestions?

 

[RMerlin]

OpenDNS doesn't work with Asuswrt, as it doesn't follow the RFCs when it comes to NXDOMAIN answers.

 

[linkmaster]

OpenDNS doesn't work with Asuswrt, as it doesn't follow the RFCs when it comes to NXDOMAIN answers.

Is that only with ver 354.* beta? , 270.26 here and openDNS is working 100%.

 

[RMerlin]

Is that only with ver 354.* beta? , 270.26 here and openDNS is working 100%.

If you enter the OpenDNS IPs in the router and have your client use the router's IP as their own DNS server, then all lookup queries will fail because it will first try to append your LAN's domain. OpenDNS doesn't return a proper NXDOMAIN error, so it means that any IP you try to resolve gets resolved to OpenDNS's error page.

I believe it's possible to disable the NXDOMAIN hijacking in OpenDNS's control panel if you use an actual account with them, but I don't know the details as I don't use OpenDNS.

If you directly use OpenDNS's servers on your clients then it will also work normally, as clients won't append the local domain suffix.

 

[gamewarden3006]

HMM....

I have not actually used openDNS is quiet a while. just used it as an example.

I hated getting redirected to there page if lookup failed.

the servers I have been using are level 3 communications. 4.2.2.X

it has always worked fine before. I recently upgraded FW a few weeks ago.


I'm just wondering id something has changed in the newer firmware or if it inadvertently changed a setting during upgrade somewhere that I am just missing...

 

[gamewarden3006]

I got the issue figured out.

I upgraded to 354.29 beta1 and still did not work...

I then downgraded to 270.26 and it is working just fine now.

any idea what might be going on in the newer FW?

 

[RMerlin]

No idea, I will have to see if I can reproduce the issue.

I know that there are a few odd things about DNS handling under Asuswrt, and it's not something new. This is something I mean to look more closely into at some point, just never got around to it yet.

Can you see if you have the same problem with Asus's 3.0.0.4.354? That will give me a pointer if you can confirm whether the issue also exists under the original firmware or not.

 

[linkmaster]

If you enter the OpenDNS IPs in the router and have your client use the router's IP as their own DNS server, then all lookup queries will fail because it will first try to append your LAN's domain. OpenDNS doesn't return a proper NXDOMAIN error, so it means that any IP you try to resolve gets resolved to OpenDNS's error page.

I believe it's possible to disable the NXDOMAIN hijacking in OpenDNS's control panel if you use an actual account with them, but I don't know the details as I don't use OpenDNS.

If you directly use OpenDNS's servers on your clients then it will also work normally, as clients won't append the local domain suffix.

Saying that....the router here (270.26) has exactly that , OpenDNS on the router and the router as the DNS address on both of the kids PCs, tablets , gaming consoles etc and they don't have any problems at all with browsing the web etc.

 

[RMerlin]

Saying that....the router here (270.26) has exactly that , OpenDNS on the router and the router as the DNS address on both of the kids PCs, tablets , gaming consoles etc and they don't have any problems at all with browsing the web etc.

Must be because you aren't using a local domain then, so your queries don't get the local domain appended to them. That's what's causing issues with the NXDOMAIN reports. Either that, or you have an OpenDNS account without the error page redirection enabled.