Possible Linksys Static DNS Fix
So today I've been messing around with a Netgear Nighthawk AC1750 because I wasn't able to get OpenDNS to work with a Linksys AC1750. The Nighthawk was having the same issue. When I checked 'ipconfig /all' it said the DNS IP was 192.168.1.1 and it wasn't blocking websites. I made sure my public IP was synced with OpenDNS and OpenDNS Server IPs were entered correctly. Was about to return Nighthawk but decided to try one more thing. I deleted my network from the OpenDNS Dashboard > Settings tab, then re-added it. After that, OpenDNS started working again. I checked 'ipconfig /all' and it still says my DNS IP is 192.168.1.1 but I think that's just how the new routers are setup. They're actually using whatever DNS IP you entered but it just doesn't say it on CMD prompt. So if anyone is having issues with OpenDNS not working with a new router, try deleting your network from the OpenDNS Dashboard > Settings tab, then re-adding it again.
-
Unfortunately your fix is not a fix.
You don't need to delete and re-add your dashboard network, under no circumstances. The only think you need to do is to keep your IP address information updated at your dashboard network, preferably with an Updater.
And no, the fact that DHCP configures your router's IP address as DNS server address is and was always totally normal. External DNS server addresses should not appear on the DHCP/LAN side, just on the WAN side, because this is your router which is to forward DNS queries to the DNS service, not your end user devices.
-
Well my old Linksys E1200 router would show the OpenDNS IPs when I checked 'ipconfig /all'. But it only shows 192.168.1.1 with the newer Linksys AC1750 & Nighthawk AC1750 routers. I think it does that with all newer routers. OpenDNS wasn't working with Linksys AC1750 or Nighthawk AC1750 so I tried deleting/re-adding my Network in the OpenDNS Dashboard and it started working again. But it still shows 192.168.1.1 in 'ipconfig /all'.
-
Yes, the old Linksys firmware was really a shame. You could configure an alternative DNS service only on the DHCP/LAN side, leading to several troubles like breaking internal network name resolution. The newer firmware seems to keep up more with the proper technology, so you see your router's IP address as the DNS server address on your end use devices as should be.
And again, the only thing you still need to do is to run an Updater in your network to keep your IP address information updated at OpenDNS. The same effect comes with deleting and re-adding the network, but then you must also recreate all your settings from the old network in the new network. Therefore this is not the way to go.
Please sign in to leave a comment.
Comments
3 comments