gmonks Posted March 16, 2015 Posted March 16, 2015 Hi all, Got Internet issues here. What baffles me is a the servers and a couple of PCs are okay. We recently moved ISP and I have changed all the settings etc. Google Chrome's error is [h=1] ERROR CODE DNS_PROBE_FINISHED_NXDOMAIN [/h] Any ideas? Any help would be really appreciated! George
Gaz Posted March 16, 2015 Posted March 16, 2015 OK going off that error message alone I would take a look at your DNS settings for your network and internet. Have you changed your DNS servers to your new ISP? You could try using Googles (8.8.8.8 8.8.4.4) or OpenDNS 208.67.222.222 208.67.220.220) servers
gmonks Posted March 16, 2015 Author Posted March 16, 2015 OK going off that error message alone I would take a look at your DNS settings for your network and internet. Have you changed your DNS servers to your new ISP? You could try using Googles (8.8.8.8 8.8.4.4) or OpenDNS 208.67.222.222 208.67.220.220) servers I have changed it our new ISP yes...
Gaz Posted March 16, 2015 Posted March 16, 2015 Restart the DNS service? Are IE and FF also effected? Clear the cache from Chrome.
gmonks Posted March 16, 2015 Author Posted March 16, 2015 Restart the DNS service? Are IE and FF also effected? Clear the cache from Chrome. Restarted DNS. IE also affected.
gmonks Posted March 16, 2015 Author Posted March 16, 2015 Flush the DNS cache from an effected PC. Tried that too! No such luck
Gaz Posted March 16, 2015 Posted March 16, 2015 I'm almost out of ideas but I'd definitely try changing the DNS ips on an effected PC if you haven't already tried.
gmonks Posted March 16, 2015 Author Posted March 16, 2015 Sorted. For some strange reasons in the DNS settings under the router the IP address had removed itself...ugh!!
kennysarmy Posted March 16, 2015 Posted March 16, 2015 Nice one, we had internet issues last week - it took us four hours to diagnose it as a faulty port on our core switch (linked to the RM router!) - after thinking it was a DHCP/DNS. RM confirmed they could PING our core switch from their router - but in later troubleshooting we could not PING their router from our switch! Moving to another port on the switch solved the problem!
gmonks Posted March 16, 2015 Author Posted March 16, 2015 Nice one, we had internet issues last week - it took us four hours to diagnose it as a faulty port on our core switch (linked to the RM router!) - after thinking it was a DHCP/DNS. RM confirmed they could PING our core switch from their router - but in later troubleshooting we could not PING their router from our switch! Moving to another port on the switch solved the problem! That was the similar frustration I was experiencing!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now