Patrick9876
Regular Contributor
RT-AC86U Merlin 384.18
Yesterday I was getting some dropped wireless connections so I rebooted my router (for the 1st time in over a month). After the reboot all powered up devices - 2 computers, 3 NAS devices, 1 thermostat on a guest network - showed in the router's client list except for 1 NAS. I had no trouble accessing the NAS by address but name resolution failed on the 2 computers. I have a CNAME records in dnsmasq.conf.add mapping 2 names to the "real" host name and resolution of all 3 names failed (according to NSLOOKUP on the computers).
I didn't want to reboot the router again so I rebooted the NAS . No logic behind that; just desperation. And it worked!
So, finally, some questions.
Yesterday I was getting some dropped wireless connections so I rebooted my router (for the 1st time in over a month). After the reboot all powered up devices - 2 computers, 3 NAS devices, 1 thermostat on a guest network - showed in the router's client list except for 1 NAS. I had no trouble accessing the NAS by address but name resolution failed on the 2 computers. I have a CNAME records in dnsmasq.conf.add mapping 2 names to the "real" host name and resolution of all 3 names failed (according to NSLOOKUP on the computers).
I didn't want to reboot the router again so I rebooted the NAS . No logic behind that; just desperation. And it worked!
So, finally, some questions.
- Is there some kind of DNS handshake that takes place between the router and the local devices when the router initializes? If so, what would cause the failure of DNS handshake to fail between the router and the NAS (and not between the router and other devices?
- Is the router's client list just related to DNS of did the missing client entry indication that the router knew nothing about the NAS? And if the latter, why were the computers able to access the NAS? Had the cached ARP stuff from when the router knew about the NAS? (And if that question is stupid, try to let me know why.)
- Could I have done something less disruptive than rebooting the NAS? Would unplugging and replugging the Ethernet cable been enough?