NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jamestx10
Mar 23, 2017Aspirant
6.6.1 on Ultra 6 Loses DNS lookup after a few days
I have my router configured as the DNS server in the network settings. It can reach the router fine but it fails to resolve addresses after a few days. I reboot the NAS and it is good to go again for...
jak0lantash
Mar 28, 2017Mentor
jamestx10 wrote:
/net/connman/service/ethernet_001f33ea8125_cable Ethernet = [ Method=auto, Interface=eth0, Address=00:1F:33:EA:81:25, MTU=1500 ] IPv4 = [ Method=dhcp, Address=10.10.10.20, Netmask=255.255.255.0, Gateway=10.10.10.1 ]
/net/connman/service/ethernet_001f33ea8124_cable Ethernet = [ Method=auto, Interface=eth1, Address=00:1F:33:EA:81:24, MTU=1500 ] IPv4.Configuration = [ Method=manual, Address=10.101.1.3, Netmask=255.255.255.0 ]
Your configuration is correct.
Eth0: 10.10.10.20/24, GW 10.10.10.1, DNS 10.10.10.1
Eth1: 10.101.1.3/24, no GW, no DNS
This is exactly the configuration I have on my NAS and it's working OK.
You could try to restart connmand, but it's just easier to reboot the NAS.
After the reboot, double check that both NICs still have the same configuration, from the GUI and using the command I give you.
Try again to resolve google.com with a ping.
jak0lantash
Mar 29, 2017Mentor
jak0lantash wrote:
jamestx10 wrote:
/net/connman/service/ethernet_001f33ea8125_cable Ethernet = [ Method=auto, Interface=eth0, Address=00:1F:33:EA:81:25, MTU=1500 ] IPv4 = [ Method=dhcp, Address=10.10.10.20, Netmask=255.255.255.0, Gateway=10.10.10.1 ]
/net/connman/service/ethernet_001f33ea8124_cable Ethernet = [ Method=auto, Interface=eth1, Address=00:1F:33:EA:81:24, MTU=1500 ] IPv4.Configuration = [ Method=manual, Address=10.101.1.3, Netmask=255.255.255.0 ]Your configuration is correct.
Eth0: 10.10.10.20/24, GW 10.10.10.1, DNS 10.10.10.1
Eth1: 10.101.1.3/24, no GW, no DNS
This is exactly the configuration I have on my NAS and it's working OK.
You could try to restart connmand, but it's just easier to reboot the NAS.
After the reboot, double check that both NICs still have the same configuration, from the GUI and using the command I give you.
Try again to resolve google.com with a ping.
- jamestx10Mar 30, 2017Aspirant
It is currently in a failure state. Cannot resolve DNS names.
root@NAS:~# ping google.com ping: bad address 'google.com' root@NAS:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: seq=0 ttl=58 time=2.615 ms 64 bytes from 8.8.8.8: seq=1 ttl=58 time=2.498 ms 64 bytes from 8.8.8.8: seq=2 ttl=58 time=2.539 ms ^C --- 8.8.8.8 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 2.498/2.550/2.615 ms
I can SSH in on both Eth0 and Eth1 so the network link is up. I can also access the web GUI and it shows no change in the network settings. I DL the logs but have no idea where to look in them for any issues.
for a_service in $(connmanctl services | awk '{ printf $3" " }'); do connmanctl services $a_service; done /net/connman/service/ethernet_001f33ea8125_cable Type = ethernet Security = [ ] State = ready Favorite = True Immutable = False AutoConnect = True Name = Wired Ethernet = [ Method=auto, Interface=eth0, Address=00:1F:33:EA:81:25, MTU=1500 ] IPv4 = [ Method=dhcp, Address=10.10.10.20, Netmask=255.255.255.0, Gateway=10.10.10.1 ] IPv4.Configuration = [ Method=dhcp ] IPv6 = [ ] IPv6.Configuration = [ Method=off ] Nameservers = [ 10.10.10.1 ] Nameservers.Configuration = [ 10.10.10.1 ] Timeservers = [ 10.10.10.26, time-a.netgear.com, 10.10.10.1 ] Timeservers.Configuration = [ 10.10.10.26, time-a.netgear.com ] Routes = [ ] Routes.Configuration = [ ] Domains = [ NULEAF ] Domains.Configuration = [ ] Proxy = [ Method=direct ] Proxy.Configuration = [ ] Provider = [ ] /net/connman/service/ethernet_001f33ea8124_cable Type = ethernet Security = [ ] State = ready Favorite = True Immutable = False AutoConnect = True Name = Wired Ethernet = [ Method=auto, Interface=eth1, Address=00:1F:33:EA:81:24, MTU=1500 ] IPv4 = [ Method=manual, Address=10.101.1.3, Netmask=255.255.255.0 ] IPv4.Configuration = [ Method=manual, Address=10.101.1.3, Netmask=255.255.255.0, Gateway=10.10.10.1 ] IPv6 = [ ] IPv6.Configuration = [ Method=off ] Nameservers = [ ] Nameservers.Configuration = [ ] Timeservers = [ 10.10.10.26, time-a.netgear.com, 10.10.10.1 ] Timeservers.Configuration = [ 10.10.10.26, time-a.netgear.com ] Routes = [ ] Routes.Configuration = [ ] Domains = [ ] Domains.Configuration = [ ] Proxy = [ Method=direct ] Proxy.Configuration = [ ] Provider = [ ]- jak0lantashMar 30, 2017Mentor
Not sure if that's the issue, but there is indeed a difference between now and earlier. Eth1 shouldn't have a default gateway and it didn't, but now it does. Any chance you could run Wireshark on the PC connected to eth1, ping google.com on the NAS and look at Wireshark to see if you receive DNS queries from the NAS?
- jamestx10Mar 31, 2017Aspirant
Well the issue is worse then I first thought. I did not have time last night to wireshark so I left it. This moring the NAS has locked up. No GUI, No SSH, No respond to ping, even the front power button would not make the display light up. Hard reboot and it is back up.
So it seems that the failure of DNS to resolve is just one of the first signs that I get that the system is going to lock up in the next 12 - 24 hours. I downloaded logs again as soon as the system was back up but I don't know what to look for in them. Should I try reinstalling 6.1.1
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!