Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Google DNS Strangeness
Options
-
17-10-2013 12:40pm#1I use the Google DNS server and for a while now I've noticed something a bit odd with it - every few days, or at least I only notice it every few days, it seems to completely lose the Daily Mail (www.dailymail.co.uk) so I'm unable to connect to it and I don't think I've ever noticed it lose anything else. Usually it'll be back after a short period of time but it just seems a bit strange. Anyone have any ideas as to why this would be happening?
Google Primary DNS ServerC:\Users\John>nslookup www.dailymail.co.uk 8.8.8.8 Server: google-public-dns-a.google.com Address: 8.8.8.8 *** google-public-dns-a.google.com can't find www.dailymail.co.uk: Server failed
Google Secondary DNS ServerC:\Users\John>nslookup www.dailymail.co.uk 8.8.4.4 Server: google-public-dns-b.google.com Address: 8.8.4.4 *** google-public-dns-b.google.com can't find www.dailymail.co.uk: Server failed
UPC DNS ServerC:\Users\John>nslookup www.dailymail.co.uk 89.101.160.8 Server: ie-dub01a-dns01o.upc.ie Address: 89.101.160.8 Non-authoritative answer: Name: a1613.g.akamai.net Addresses: 88.221.93.89 88.221.93.95 Aliases: www.dailymail.co.uk www.dailymail.co.uk.edgesuite.net
Google Primary DNS Server with DebugC:\Users\John>nslookup -debug www.dailymail.co.uk 8.8.8.8 ------------ Got answer: HEADER: opcode = QUERY, id = 1, rcode = NOERROR header flags: response, want recursion, recursion avail. questions = 1, answers = 1, authority records = 0, additional = 0 QUESTIONS: 8.8.8.8.in-addr.arpa, type = PTR, class = IN ANSWERS: -> 8.8.8.8.in-addr.arpa name = google-public-dns-a.google.com ttl = 12364 (3 hours 26 mins 4 secs) ------------ Server: google-public-dns-a.google.com Address: 8.8.8.8 ------------ Got answer: HEADER: opcode = QUERY, id = 2, rcode = NXDOMAIN header flags: response, want recursion, recursion avail. questions = 1, answers = 0, authority records = 1, additional = 0 QUESTIONS: www.dailymail.co.uk.Valhalla, type = A, class = IN AUTHORITY RECORDS: -> (root) ttl = 805 (13 mins 25 secs) primary name server = a.root-servers.net responsible mail addr = nstld.verisign-grs.com serial = 2013101700 refresh = 1800 (30 mins) retry = 900 (15 mins) expire = 604800 (7 days) default TTL = 86400 (1 day) ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 3, rcode = NXDOMAIN header flags: response, want recursion, recursion avail. questions = 1, answers = 0, authority records = 1, additional = 0 QUESTIONS: www.dailymail.co.uk.Valhalla, type = AAAA, class = IN AUTHORITY RECORDS: -> (root) ttl = 805 (13 mins 25 secs) primary name server = a.root-servers.net responsible mail addr = nstld.verisign-grs.com serial = 2013101700 refresh = 1800 (30 mins) retry = 900 (15 mins) expire = 604800 (7 days) default TTL = 86400 (1 day) ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 4, rcode = SERVFAIL header flags: response, want recursion, recursion avail. questions = 1, answers = 0, authority records = 0, additional = 0 QUESTIONS: www.dailymail.co.uk, type = A, class = IN ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 5, rcode = SERVFAIL header flags: response, want recursion, recursion avail. questions = 1, answers = 0, authority records = 0, additional = 0 QUESTIONS: www.dailymail.co.uk, type = AAAA, class = IN ------------ *** google-public-dns-a.google.com can't find www.dailymail.co.uk: Server failed C:\Users\John>
Google Secondary DNS Server with DebugC:\Users\John>nslookup -debug www.dailymail.co.uk 8.8.4.4 ------------ Got answer: HEADER: opcode = QUERY, id = 1, rcode = NOERROR header flags: response, want recursion, recursion avail. questions = 1, answers = 1, authority records = 0, additional = 0 QUESTIONS: 4.4.8.8.in-addr.arpa, type = PTR, class = IN ANSWERS: -> 4.4.8.8.in-addr.arpa name = google-public-dns-b.google.com ttl = 12155 (3 hours 22 mins 35 secs) ------------ Server: google-public-dns-b.google.com Address: 8.8.4.4 ------------ Got answer: HEADER: opcode = QUERY, id = 2, rcode = NXDOMAIN header flags: response, want recursion, recursion avail. questions = 1, answers = 0, authority records = 1, additional = 0 QUESTIONS: www.dailymail.co.uk.Valhalla, type = A, class = IN AUTHORITY RECORDS: -> (root) ttl = 589 (9 mins 49 secs) primary name server = a.root-servers.net responsible mail addr = nstld.verisign-grs.com serial = 2013101700 refresh = 1800 (30 mins) retry = 900 (15 mins) expire = 604800 (7 days) default TTL = 86400 (1 day) ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 3, rcode = NXDOMAIN header flags: response, want recursion, recursion avail. questions = 1, answers = 0, authority records = 1, additional = 0 QUESTIONS: www.dailymail.co.uk.Valhalla, type = AAAA, class = IN AUTHORITY RECORDS: -> (root) ttl = 589 (9 mins 49 secs) primary name server = a.root-servers.net responsible mail addr = nstld.verisign-grs.com serial = 2013101700 refresh = 1800 (30 mins) retry = 900 (15 mins) expire = 604800 (7 days) default TTL = 86400 (1 day) ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 4, rcode = SERVFAIL header flags: response, want recursion, recursion avail. questions = 1, answers = 0, authority records = 0, additional = 0 QUESTIONS: www.dailymail.co.uk, type = A, class = IN ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 5, rcode = SERVFAIL header flags: response, want recursion, recursion avail. questions = 1, answers = 0, authority records = 0, additional = 0 QUESTIONS: www.dailymail.co.uk, type = AAAA, class = IN ------------ *** google-public-dns-b.google.com can't find www.dailymail.co.uk: Server failed C:\Users\John>
UPC DNS Server with DebugC:\Users\John>nslookup -debug www.dailymail.co.uk 89.101.160.8 ------------ Got answer: HEADER: opcode = QUERY, id = 1, rcode = NOERROR header flags: response, want recursion, recursion avail. questions = 1, answers = 1, authority records = 0, additional = 0 QUESTIONS: 8.160.101.89.in-addr.arpa, type = PTR, class = IN ANSWERS: -> 8.160.101.89.in-addr.arpa name = ie-dub01a-dns01o.upc.ie ttl = 68750 (19 hours 5 mins 50 secs) ------------ Server: ie-dub01a-dns01o.upc.ie Address: 89.101.160.8 ------------ Got answer: HEADER: opcode = QUERY, id = 2, rcode = NXDOMAIN header flags: response, want recursion, recursion avail. questions = 1, answers = 0, authority records = 1, additional = 0 QUESTIONS: www.dailymail.co.uk.Valhalla, type = A, class = IN AUTHORITY RECORDS: -> (root) ttl = 600 (10 mins) primary name server = a.root-servers.net responsible mail addr = nstld.verisign-grs.com serial = 2013101700 refresh = 1800 (30 mins) retry = 900 (15 mins) expire = 604800 (7 days) default TTL = 86400 (1 day) ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 3, rcode = NXDOMAIN header flags: response, want recursion, recursion avail. questions = 1, answers = 0, authority records = 1, additional = 0 QUESTIONS: www.dailymail.co.uk.Valhalla, type = AAAA, class = IN AUTHORITY RECORDS: -> (root) ttl = 600 (10 mins) primary name server = a.root-servers.net responsible mail addr = nstld.verisign-grs.com serial = 2013101700 refresh = 1800 (30 mins) retry = 900 (15 mins) expire = 604800 (7 days) default TTL = 86400 (1 day) ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 4, rcode = NOERROR header flags: response, want recursion, recursion avail. questions = 1, answers = 4, authority records = 0, additional = 0 QUESTIONS: www.dailymail.co.uk, type = A, class = IN ANSWERS: -> www.dailymail.co.uk canonical name = www.dailymail.co.uk.edgesuite.net ttl = 2432 (40 mins 32 secs) -> www.dailymail.co.uk.edgesuite.net canonical name = a1613.g.akamai.net ttl = 3621 (1 hour 21 secs) -> a1613.g.akamai.net internet address = 88.221.93.89 ttl = 3 (3 secs) -> a1613.g.akamai.net internet address = 88.221.93.95 ttl = 3 (3 secs) ------------ Non-authoritative answer: ------------ Got answer: HEADER: opcode = QUERY, id = 5, rcode = NOERROR header flags: response, want recursion, recursion avail. questions = 1, answers = 2, authority records = 1, additional = 0 QUESTIONS: www.dailymail.co.uk, type = AAAA, class = IN ANSWERS: -> www.dailymail.co.uk canonical name = www.dailymail.co.uk.edgesuite.net ttl = 2432 (40 mins 32 secs) -> www.dailymail.co.uk.edgesuite.net canonical name = a1613.g.akamai.net ttl = 3621 (1 hour 21 secs) AUTHORITY RECORDS: -> g.akamai.net ttl = 395 (6 mins 35 secs) primary name server = n0g.akamai.net responsible mail addr = hostmaster.akamai.com serial = 1382009611 refresh = 1000 (16 mins 40 secs) retry = 1000 (16 mins 40 secs) expire = 1000 (16 mins 40 secs) default TTL = 1800 (30 mins) ------------ Name: a1613.g.akamai.net Addresses: 88.221.93.89 88.221.93.95 Aliases: www.dailymail.co.uk www.dailymail.co.uk.edgesuite.net C:\Users\John>0
Comments
-
Why are you using Google, the fastest dns (ie closest) is usually your providers. Use that unless they are having issues.0
-
+1 Plus using a US based DNS server can screw up some content delivery systems like akamai, meaning you'll get slower downloads as a result.0
-
Well I stopped using the UPC ones after a few instances where their DNS was redirecting everything to their selfcare site and preventing me from accessing anything at all. Frankly that just annoyed me enough to stop using their DNS altogether and as for the likes of akamai or other CDNs well I'm on a 150mb connection which will be increased to 200mb next week so to be honest its fast enough that I'm not really going to notice any issues there. Not to mention that according to Google they do take your location into account when their DNS server resolves an address by using the closest server to your geographic location and one of those servers is in Dublin with others throughout europe so that shouldnt be an issue either https://developers.google.com/speed/public-dns/faq?csw=1#cdn.0
-
The speed of your connection does not matter, you will be limited by the speed of the server delivering content therefore you should be connecting to local mirrors, not ones the other side of the world. Do a speedtest on an Irish server, then one a few thousand miles away and you'll see why.0
-
I understand that, what I meant was simply that even if connecting to a server in the middle of nowhere USA gave me a speed 10% of my normal connection its still going to be in the region 15mb which isn't really all that slow, even for the likes of Netflix etc.0
-
Advertisement
-
You are under the impression servers deliver to you at top speed, not so. Most web servers delivering web pages max at about 3mbit and a single web page can have many lookups and be from many servers. You do not want to be pulling web pages from the other side of the world, you need to be pulling from local ones if possible. Use your ISPs DNS, it's setup to suit their peering for the fastest connection.0
-
I've used this app from Steve Gibson in the past to find the fastest DNS server and it works quite well https://www.grc.com/dns/benchmark.htm ended up deploying my own local DNS on a Raspberry PI and haven't looked back!0
-
I've used this app from Steve Gibson in the past to find the fastest DNS server and it works quite well https://www.grc.com/dns/benchmark.htm ended up deploying my own local DNS on a Raspberry PI and haven't looked back!
Regardless of what that app says you should be using your providers as it will be internal on their network. If you really want to speed things up get a proper router like a Mikrotik that caches requests, makes a huge difference when regular lookups come from your router.0 -
smee again wrote: »Regardless of what that app says you should be using your providers as it will be internal on their network. If you really want to speed things up get a proper router like a that caches requests, makes a huge difference when regular lookups come from your router.
Have to disagree here just because it's on your ISPs internal network doesn't mean anything. Absolutely deploy a local DNS server on your LAN but not on a router use a Raspberry PI or similar much more fun and usable.0 -
Below is a benchmark against my local DNS, Googles and my ISP's (UPC) needless to say my local came out on top overall, Googles second and my ISP way down the list.
I've attached the results of the full test showing many more DNS servers not local to my ISP out performing their servers.
Final benchmark results, sorted by nameserver performance:
(average cached name retrieval speed, fastest to slowest)
172. 20. 0. 5 | Min | Avg | Max |Std.Dev|Reliab%|
+
+
+
+
+
+
+ Cached Name | 0.002 | 0.004 | 0.008 | 0.001 | 100.0 |
+ Uncached Name | 0.023 | 0.099 | 0.338 | 0.089 | 100.0 |
+ DotCom Lookup | 0.024 | 0.040 | 0.143 | 0.022 | 100.0 |
---<
>---+
+
+
+
+
+
Non-routable local internet address
Local Network Nameserver
8. 8. 4. 4 | Min | Avg | Max |Std.Dev|Reliab%|
+
+
+
+
+
+
- Cached Name | 0.008 | 0.013 | 0.022 | 0.003 | 100.0 |
- Uncached Name | 0.021 | 0.088 | 0.323 | 0.080 | 100.0 |
- DotCom Lookup | 0.013 | 0.029 | 0.104 | 0.021 | 100.0 |
---<
>---+
+
+
+
+
+
google-public-dns-b.google.com
GOOGLE - Google Inc.
8. 8. 8. 8 | Min | Avg | Max |Std.Dev|Reliab%|
+
+
+
+
+
+
- Cached Name | 0.009 | 0.013 | 0.022 | 0.003 | 100.0 |
- Uncached Name | 0.021 | 0.100 | 0.360 | 0.092 | 100.0 |
- DotCom Lookup | 0.013 | 0.023 | 0.040 | 0.007 | 100.0 |
---<
>---+
+
+
+
+
+
google-public-dns-a.google.com
GOOGLE - Google Inc.
89.101.160. 8 | Min | Avg | Max |Std.Dev|Reliab%|
+
+
+
+
+
+
- Cached Name | 0.009 | 0.031 | 0.190 | 0.046 | 100.0 |
- Uncached Name | 0.010 | 0.099 | 0.489 | 0.108 | 100.0 |
- DotCom Lookup | 0.010 | 0.018 | 0.038 | 0.008 | 100.0 |
---<
>---+
+
+
+
+
+
ie-dub01a-dns01o.upc.ie
LGI-UPC Liberty Global Operations B.V.
89.101.160. 9 | Min | Avg | Max |Std.Dev|Reliab%|
+
+
+
+
+
+
- Cached Name | 0.008 | 0.040 | 0.189 | 0.052 | 100.0 |
- Uncached Name | 0.013 | 0.096 | 0.465 | 0.098 | 100.0 |
- DotCom Lookup | 0.009 | 0.023 | 0.044 | 0.011 | 100.0 |
---<
>---+
+
+
+
+
+
ie-dub01a-dns02o.upc.ie
LGI-UPC Liberty Global Operations B.V.0 -
Advertisement
-
Just because they perform faster does not mean they are best for you. DNS needs your geolocatation, (not just your public ip) to send you to the best servers for you. Your ISP knows best, but may not be the fastest.0
-
You're putting a lot of faith in the ISP. I'm not sure about the ISPs DNS servers serving up location based records for a domain its not authoritative for either. Maybe by some prior arrangement for some content delivery services so I'd say it would certainly be the exception rather than the rule and these services will figure out where you are based on your IP and redirect you to the closest server anyway.
Anyhow I stand by it your still better off running the benchmark regularly and using what it determines to be the best from your location sticking your ISPs as the 3 & 4th in case the first stop serving your location.0 -
Download this program and run a test:
https://code.google.com/p/namebench/
It will show you the fastest DNS for you to use. For me, OpenDNS turned out to be over 90% faster than Google DNS. It takes about 30-60 minutes to run, but it is a handy tool to run every now and again.0
Advertisement