Thread: 100M DNS issue?
View Single Post
Old 01-07-2014, 13:19   #19
Kushan
cf.mega poster
 
Join Date: Dec 2010
Location: Warrington
Posts: 4,737
Kushan has a bronzed appealKushan has a bronzed appeal
Kushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appealKushan has a bronzed appeal
Re: DNS issue?

Quote:
Originally Posted by horseman View Post
SamKnows DNS sampling via Brighton brig15 and my BN3 node recorded DNS failures(or lag/prolonged response times) starting on 24June.


Usually these tend to average around 13ms.
Namebench tests indicated VM secondary DNS hit 1036ms average with 98% deviation from 6ms to 5000ms+ maximum at one point.
Jesus, that's some frightening latency.

Quote:
Originally Posted by qasdfdsaq View Post
I do wonder if anyone will ever score the equivalent IPV6 address... 8.8.8.8 was a steal for Google.
I believe Level 3 actually own the address, Google just leases it from them.

Facebook's is the best IPv6 address I've seen so far and even that's nothing amazing:

2a03:2880:2110:df07:face:b00c:0:1

As all publicly routable IPv6 addresses need to start with 2 (as far as I understand), I guess the nearest equivalent to 8.8.8.8 would have to be something like 2222::2222 or something else symmetrical like 2345::5432.
Kushan is offline   Reply With Quote