DNS Server died on me, what am I supposed to do?

[cloudropis]

Completely out of nowhere every single device in my house stopped connecting to the internet. They'd connect to the router fine, but trying to do anything requiring a connection, from opening Steam to simply browsing the web, led to generic connection errors and a DNS_PROBE_FINISHED_BAD_CONFIG from Chrome. For some reason the only platform which kept working fine was Telegram.

I managed to fix this on my home PC by manually setting my DNS to Google's (8.8.8.8), and I think I'll be able to do the same for my mobile devices, but I have no idea regarding my Sky decoder. Is there anything I can do to fix this?

EDIT already rebooted my router several times, as well as flushing the dns through cmd prompt

 

[BuddhaSkoota]

Completely out of nowhere every single device in my house stopped connecting to the internet. They'd connect to the router fine, but trying to do anything requiring a connection, from opening Steam to simply browsing the web, led to generic connection errors and a DNS_PROBE_FINISHED_BAD_CONFIG from Chrome. For some reason the only platform which kept working fine was Telegram.

I managed to fix this on my home PC by manually setting my DNS to Google's (8.8.8.8), and I think I'll be able to do the same for my mobile devices, but I have no idea regarding my Sky decoder. Is there anything I can do to fix this?

EDIT already rebooted my router several times, as well as flushing the dns through cmd prompt

Change the LAN DHCP on the router to the Google DNS (8.8.8.8 and 8.8.4.4). All devices will have those DNS addresses assigned from the router.

 

[cloudropis]

Completely out of nowhere every single device in my house stopped connecting to the internet. They'd connect to the router fine, but trying to do anything requiring a connection, from opening Steam to simply browsing the web, led to generic connection errors and a DNS_PROBE_FINISHED_BAD_CONFIG from Chrome. For some reason the only platform which kept working fine was Telegram.

I managed to fix this on my home PC by manually setting my DNS to Google's (8.8.8.8), and I think I'll be able to do the same for my mobile devices, but I have no idea regarding my Sky decoder. Is there anything I can do to fix this?

EDIT already rebooted my router several times, as well as flushing the dns through cmd prompt

Change the LAN DHCP on the router to the Google DNS (8.8.8.8 and 8.8.4.4). All devices will have those DNS addresses assigned from the router.

Done, it's working now. Can I keep it like this indefinitely or will I have to switch back to the automatic DNS server somewhere down the line? What may have caused this, something out of my/my ISP's control or should I give them a call?

 

[bill001g]

The default DNS setting use your router as a proxy and a DNS server normally run by the ISP as the DNS server.

In some cases it is the router trying to be helpful and cache data and it has bugs or it can be the ISP DNS is down.

Google DNS is one of the best because the 8.8.8.8 ip address actually is duplicated in many cities around the world so it tends to get the best latency. Problem is like most things related to google is it like to collect information. You could use 4.2.2.2 which is run by level3 and works similar to 8.8.8.8

I always use the google ones and it tends to always be stable.

 

[anotherdrew]

I like openDNS because of the filtering features ( I have teenagers). I am a bit bummed they don't offer IPv6 filtering.

 

[bill001g]

I like openDNS because of the filtering features ( I have teenagers). I am a bit bummed they don't offer IPv6 filtering.

Your teenagers are lazy then Google used to recommend the word "bypass" when you searched opendns since it was searched so much.

 

[androbourne]

You need to be careful about running DNS from the router instead of the DNS server. Especially when on a domain network. You have more control over DNS when on the server (think records). Because it is moved to the router, those records will most likely not come over. So custom records like a www., A hosts may not function properly. You will have to do work a rounds.

Also on a domain network PC DNS can be effected and you may get more Dcom and other related errors in the server log and may have communication issues etc....

So with that in mind. If you are on a domain, I would recommend you spin up a new DNS server or fix that one and move it back to the server. It is also industry standard on a domain network to not have DNS running from the router and it running on a server.

 

[cloudropis]

Some of the stuff you people mentioned flew over my head, sorry I'm not very good at this. I know what a DNS does on a theorical level, but not the practical applications.

A few days later I still have the same problem, using the default DNS doesn't let me connect to the internet but I'm using Google's through my router's page. Everything seems sort of fine, but some rare pages take very long to load for some reason, or don't load at all, and I just noticed some browser (Chrome) downloads don't work. For example, https://www.thinkbroadband.com/download packets show up in my download queue, go at 10kb/s for a few seconds, and then just stop. Why is that? Is switching to Google's DNS server to blame?

The default DNS is on my ISP's end, right? So if I want this issue fixed it's them I should bother through customer support, right?

Is there any reason I can't just use Google's DNS indefinitely? I was lazy because I had a test to prepare for and I really needed the internet, so I didn't bother to think if it's an optimal long-term solution. I'm getting the problems I've mentioned at the beginning of the post, but I don't know if google's DNS is at fault.

 

[bill001g]

I use google dns all the time with no issue.

Make sure when you do a IPCONFIG /ALL it shows the dns server and not your router ip.

DNS is only looked up 1 time. After it knows the actual IP address of the site it will use that and not the name. So once a download starts the DNS is not used again. The PC will actually keep the DNS lookup in memory for a short period of time so if say a web browser opens a bunch of pages on the same site it will only look the first one up. This is why you see people saying to do things like flush the dns since it will sometime keep it longer than it should