Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Google Public DNS
Google Public DNS
Posted by Eased, 12-25-2012, 10:03 AM |
Hello,
Anyone else experiencing issues with Google's public DNS servers?
8.8.8.8
8.8.4.4
I have servers in multiple geo-locations having issues on these DNS servers.
Timeouts or no reply at all for DNS queries... |
Posted by Snoork Hosting, 12-25-2012, 10:39 AM |
No issues here. |
Posted by HostUS - Alexander, 12-25-2012, 01:35 PM |
Quote:
Originally Posted by Eased
Hello,
Anyone else experiencing issues with Google's public DNS servers?
8.8.8.8
8.8.4.4
I have servers in multiple geo-locations having issues on these DNS servers.
Timeouts or no reply at all for DNS queries...
|
Hello,
YES! I have been stressing about this all day, i just can't get my VPS to resolve domain names
All day i have been trying to find the problem lol.
Thanks for the heads up!
Happy holidays! |
Posted by sentabi, 12-25-2012, 01:50 PM |
Quote:
Originally Posted by Eased
Hello,
Anyone else experiencing issues with Google's public DNS servers?
8.8.8.8
8.8.4.4
I have servers in multiple geo-locations having issues on these DNS servers.
Timeouts or no reply at all for DNS queries...
|
no issue here |
Posted by OasisDedicated, 12-25-2012, 07:09 PM |
Quote:
Originally Posted by Eased
Hello,
Anyone else experiencing issues with Google's public DNS servers?
8.8.8.8
8.8.4.4
I have servers in multiple geo-locations having issues on these DNS servers.
Timeouts or no reply at all for DNS queries...
|
good here. most likely it is not google's network problem.
please try nslookup domain and see what the message. |
Posted by TmzHosting, 12-26-2012, 12:18 AM |
We do not have any issues with this. We use google's DNS on a lot of our services and they have been running with 100% uptime.
Maybe only specific areas were affected?
- Daniel |
Posted by ibee, 12-26-2012, 02:41 AM |
no issues for us, it may be specific to your case, check with your ISP or network provider. |
Posted by zsuatt, 12-26-2012, 03:58 AM |
maybe it was also affected by the AWS outage? :p |
Posted by TmzHosting, 12-26-2012, 08:39 AM |
Quote:
Originally Posted by zsuatt
maybe it was also affected by the AWS outage? :p
|
What was the AWS outage? Amazons outage?
- Daniel |
Posted by Host4Geeks-Kushal, 12-26-2012, 09:43 AM |
Quote:
Originally Posted by TmzHosting
What was the AWS outage? Amazons outage?
- Daniel
|
Yup! AWS had an outage just before Chirstmas and Netflix's services were greatly disrupted due to this. |
Posted by TmzHosting, 12-26-2012, 01:46 PM |
Couldn't watch NetFlix! Just shows you how much we rely on these things.
- Daniel |
Posted by pingedNET-Zach, 12-26-2012, 05:55 PM |
No problem here we use google dns all over the place. |
Posted by zsuatt, 12-26-2012, 05:56 PM |
Quote:
Originally Posted by PromptSpace-Kushal
Yup! AWS had an outage just before Chirstmas and Netflix's services were greatly disrupted due to this.
|
Yep, there was an outage on christmas eve. It took Netflix and a bunch of other services with it too.. |
Posted by Inertia Networks, 12-26-2012, 08:21 PM |
Google DNS has always been slow/non-responsive to me. |
Posted by dcdan, 12-26-2012, 08:24 PM |
We always add 4.2.2.1 + 4.2.2.2 to the mix, just in case. |
Posted by DavidBee, 12-26-2012, 10:03 PM |
Quote:
Originally Posted by dcdan
We always add 4.2.2.1 + 4.2.2.2 to the mix, just in case.
|
If you plan on using them I would suggest using 209.244.0.3 and 209.244.0.4 as these would route to the closest servers. |
Posted by dcdan, 12-26-2012, 10:09 PM |
Quote:
Originally Posted by David-Host Surf UK
If you plan on using them I would suggest using 209.244.0.3 and 209.244.0.4 as these would route to the closest servers.
|
Thanks - was not aware of that. Added to our deployment scripts! |
Posted by dcdan, 12-26-2012, 10:23 PM |
I just found a list of public dns servers, hope it will help someone else:
http://pcsupport.about.com/od/tipstr...ns-servers.htm
By the way, it seems that 4.2.2.x IPs also route to closest servers
(just tested this from several nodes across the globe). |
Posted by Losvre, 12-30-2012, 05:16 PM |
Maybe it sounds stupid but why don't you use your own resolvers and add a third party like google for extra reduncancy? |
Posted by dcdan, 12-30-2012, 07:08 PM |
We had our own resolvers in the past. It was a pain to add new server ip ranges to the allowed hosts in named.conf |
Posted by Eased, 12-31-2012, 04:33 AM |
Quote:
Originally Posted by Losvre
Maybe it sounds stupid but why don't you use your own resolvers and add a third party like google for extra reduncancy?
|
Depends on what your using the server for.
Of course, for the services that NEED that kind of redundancy yes. For those that don't its easier and less to manage to just throw in public external DNS records. |
Posted by Losvre, 01-03-2013, 12:10 PM |
Quote:
Originally Posted by Eased
Depends on what your using the server for.
Of course, for the services that NEED that kind of redundancy yes. For those that don't its easier and less to manage to just throw in public external DNS records.
|
I have the feeling that most shared hosting servers are depended on public DNS... I hope I am wrong |
Posted by RaidLogic, 01-03-2013, 08:53 PM |
We have no issues at all with google dns servers. |
Add to Favourites Print this Article
Also Read
Uk2 down? (Views: 980)