Menu
What's new
By:
Filters Better Search

Latest firmware has stopped local DNS connections

  • 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!

W

WannabeMKII

Occasional Visitor
I've just updated my N66U to the latest firmware and now I'm unable to use DNS names to connect to my various devices, instead I have to use local IP addresses.

Any idea why this would happen and how I can resolve?

Would obviously like to keep it as DNS, as it 'used' to work locally and remotely, but now it doesn't work locally.
 
What version of the firmware did you previously have?
Did you do a factory reset when you updated the firmware?
How are you connecting to the devices and what is your client software? ftp, nfs, samba, etc.
Have you tried connecting from another PC?
Have you made any changes to Parental Control > DNS Filtering or LAN > DHCP Server > DNS and WINS Server Setting?

What is the output of nslookup?
 
Last edited:
You did not say but if your PC's are Windows they do not always use DNS to communicate. Try setting the Samba to Master Browser, turn on WINS and enter the IP address of your router in the DHCP WINS settings.

Sent from my Amazon Tate using Tapatalk
 
Sorry for the lack of details and thanks for the help.

I came from 378.52_2 and it's on Windows machines. But since then, a Synology NAS is unable to connect either.

There's nothing in the 'Parental Controls' or in the 'DHCP' settings under 'DNS and WINS Server Settings'. I've tried populating them with different details, but still no better.

The output of the NSLOOKUP is my WAN IP.

Any other ideas?
 
WannabeMKII said:
But since then, a Synology NAS is unable to connect either.
Click to expand...
Connect to what? Or do you mean the opposite - your PC cannot connect to the NAS?

Have you tried connecting from another PC?
The output of the NSLOOKUP is my WAN IP.
Click to expand...
That can't be true. It should either show your routers LAN IP (e.g. 192.168.1.1) or the IP of an external DNS server (e.g. 8.8.8.8 = Google DNS).
 
From Network Map go to Usb Application, Media Services and Servers, Network Place (Samba)... make sure Workgroup is set the same as the rest of your Windows PC's. Check Force as Master Browser and Set as WINS Server. Apply settings. Go to LAN, DHCP Server and in the Wins Server block enter the IP of your router. Apply settings. All of your PC's that get a dynamic IP will be able to "see" each other. If your NAS has a static IP set the WINS in its networking to the IP of your router. May take a while for the Windows Networking on each device to exchange information with other devices.
 
@bbunge I understand why you're suggesting WINS, but unless the OP has (or had) a requirement for it (i.e. NetBIOS browsing across subnets) it is introducing a whole new layer of complexity into the troubleshooting process.

Just my 2 cents.
 
Where were you storing the dns entries before? Were they configured on the router with dnsmasq or similar or external?
 
Where were these entries configured? Was it on the router with dnsmasq or similar or something external?
 
Well, at first I was unsure that you could resolve a host name to IP address on an Asus router. That is why I set up the router as a master browser and WINS server. Old guys fall back to what they know works. Remember the LMHOSTS file? We used that to enable NetBT communications from a client on Guam back to a server in the states almost 20 years ago.

I looked into the settings in NVRAM in my RT-N66R and discovered that client_info_tmp= contains a listing of host names to IP to MAC Addresses. This list may be what is used to do internal name resolution.

If you did an upgrade and did not do a factory reset it is possible this list has wrong host to IP matches. You could do a factory reset to clear all the settings then reconfigure the router. Or clear just the one setting using: nvram set client_info_tmp=

For a better client cleaning of NVRAM use: nvram set nmp_client_list= && nvram set client_info_tmp= && nvram set webdav_smb_pc= && nvram commit
 
I've had the same issue on the AC66U in a mixed network. I'm wondering if it's related to one of these lines in /etc/dnsmasq.conf:

dhcp-option=lan,6,208.67.222.222,208.67.220.220,0.0.0.0
dhcp-option=lan,252,"\n"

Shouldn't the 0.0.0.0 be 192.168.1.1? Also, a newline character seems odd to me, but I don't know much about dnsmasq.

edit: was hoping to avoid a factory reset, ended up doing it anyway. no change
 
Last edited:
Thanks for all the replies, I've tried some of the suggestions, but it's not resolved it.

However, I'm not sure I've explained it as clearly as it could've been, so I'll start again.

I use DDNS to access my network remotely and to allow some services can connect in, such as Synology to backup to each other. However, since installing the latest update, things get as far as the router, then stop. I also used this DDNS to connect to things internally rather than by IP, as it's saves me switching between IP and DDNS when local or remote, but again, this isn't working either.

When I run an NSLOOKUP to the DDNS, it returns my external IP and the service is registering fine.

So not sure what's happening and why things appear to be getting 'stuck' when hitting the router?

Any other ideas, otherwise, I'll have to roll back to an earlier firmware, but I'd like to know what's stopping things...?
 
cockytrumpet said:
I've had the same issue on the AC66U in a mixed network. I'm wondering if it's related to one of these lines in /etc/dnsmasq.conf:

dhcp-option=lan,6,208.67.222.222,208.67.220.220,0.0.0.0
dhcp-option=lan,252,"\n"

Shouldn't the 0.0.0.0 be 192.168.1.1? Also, a newline character seems odd to me, but I don't know much about dnsmasq.

edit: was hoping to avoid a factory reset, ended up doing it anyway. no change
Click to expand...

The first rule seems to be the problem, you are giving clients the OpenDNS IP addresses in addition to the router. For local name resolution you need to use the router only. 0.0.0.0 is not a problem, from the dnsmasq docs:-

The special address 0.0.0.0 is taken to mean "the address of the machine running dnsmasq".
Click to expand...

Look for a web gui option to specify the router as the exclusive dns forwarder for all your local network (I currently use a custom conf file). dnsmasq will know the local IP address of everything in its static dhcp list.

The option 252 is useful, it reduces network traffic from Windows 7 machines continuously asking for proxy information I recall.
 
WannabeMKII said:
I use DDNS to access my network remotely and to allow some services can connect in, such as Synology to backup to each other. However, since installing the latest update, things get as far as the router, then stop. I also used this DDNS to connect to things internally rather than by IP, as it's saves me switching between IP and DDNS when local or remote, but again, this isn't working either.

When I run an NSLOOKUP to the DDNS, it returns my external IP and the service is registering fine.

So not sure what's happening and why things appear to be getting 'stuck' when hitting the router?

Any other ideas, otherwise, I'll have to roll back to an earlier firmware, but I'd like to know what's stopping things...?
Click to expand...
Anyone any ideas?
 
Arghhh... I've just rolled back to 378.52_2 as that's when it was last working and it's not resolved it.

What can I do next, as this is a bit of a show stopper now as nothing can connect into my network via DDNS name :(
 
WannabeMKII said:
Any idea's what I can try next?
Click to expand...

You said it used to work locally, so, the one thing you can try, which I'm sure you're trying to avoid, is a restore to factory default (and re-enter your settings, of course). It's a bit like doing a fresh install of Windows: once you've bitten the bullet and set aside the time, it's a very satisfying process - time-consuming rather than difficult. And it can cure a whole gamut of ills. Go for it.
 
Last edited:
You must log in or register to reply here.

Similar threads

icanfly
DNS fails for local devices when there is no WAN!
Replies
2
Views
446
icanfly
icanfly
X
RT-AX58U sudden DNS problem - URGENT
Replies
14
Views
649
dave14305
dave14305
S
Adding DNS entries for local machines
Replies
5
Views
2K
ColinTaylor
C
J
DNS rewrite for internal clients to resolve hostname via adguard home and unbound
Replies
12
Views
4K
jata
J
RMerlin
  • Locked
Release Asuswrt-Merlin 3004.388.5 is now available
12 13 14
Replies
260
Views
34K
RMerlin
RMerlin
Similar threads
Thread starter Title Forum Replies Date
E WebUI not working - AX86U (latest Merlin firmware) Asuswrt-Merlin 5
Z latest firmware for RT AX-86U - bug Asuswrt-Merlin 13
J Asus RT-AC68R /w latest Merlin 386.12 firmware - Openvpn client issue Asuswrt-Merlin 2
J Solved *SOLVED* Asus RT-AX86U Pro on latest Merlin 3004.388.4, cannot get RT-AC68U (on any firmware) to connect as a AI Mesh Node Asuswrt-Merlin 3
P OVPN Problem. Asus rt ax56u (latest merlin firmware Asuswrt-Merlin 9
L slight bug in latest firmware version (GT-AXE16000_388.2_2) of merlin.. says there is a new version available id 2.2 and flashes it at the top Asuswrt-Merlin 5
V Difficulty Updating to latest firmware RT-AX58U_388.2_2_puresqubi.w (existing AI mesh set-up) Asuswrt-Merlin 3
dgraham78 Traffic Analyzer Statistics showing no data (Asus RT-AX86U) on latest stable firmware Asuswrt-Merlin 2
L Does the latest AsusWRT/Merlin FW has a memory leak? Asuswrt-Merlin 20
C GT-AXE 16000 Latest Merlin and latest Stock both have memory leaks Asuswrt-Merlin 4

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

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

Members online

Total: 688 (members: 26, guests: 662)
Top