how long does it normally take for a new account to be setup?
24hrs or less
i.e. within a day
why does everyone tell me to traceroute 216.81.59.173?
mercutio: http://www.reddit.com/r/networking/comments/1875et/best_use_of_dns_routing_skillset_and_ccie/
mercutio: Because the Reddit hivemind finds it interesting this week.
static: it's everywhere though
i've seen it what one .. two three four five places so far?
correct
then i scrolled back in here
it went viral
and someone had mentioned it
there is a IPv6 one too
traceroute6 -m 120 tng.prolixium.com
em0.dax.prolixium.net
that's repeated a lot
oh damn its down
it was working this morning
maybe they needed their ipv6 addrresses back
lol
mercutio: http://www.reddit.com/r/ipv6/comments/188zpg/weve_all_seen_the_star_wars_episode_iv_traceroute/c8cuw4p
hmm
now i want something that shows different traceroutes to diff people
which would require doing it dynamically
and using ipv6 ;)
oh hmm, maybe you could do a reverse traceroute in the traceroute
and stick that in the dns'
you'd need some kind of trigger
and then to have the dns server delay giving responses until the traceroute had resolved that part
Why can't everyone just use Google?
they've got plenty of infrastructure
wut
As a ping and traceroute destination.
v4 and v6 alike
google don't stick location information in traceroutes
one name to remember... you're probably already typingit
have multiple data servers that traffic can randomly go to or through
like google seem to carry some traffic to the other side of the world :/
well sydney to amsterdam or something
also google do weird stuff, like show a ping of 24 msec, but load everything off a server 150 msec away
for things like their search
and google dns
like if you run a dns server, and look at logs, google can query from much further away addresses than 8.8.8.8
i would be very surprised if they originate queries from the ip addresses of their public dns servers
Here are the subnets from which Google Public DNS sends requests to authoritative nameservers, and their associated IATA airport codes:
64.233.162.0/24 gru
74.125.16.0/24 tpe
74.125.17.0/24 bru
74.125.18.16/29 ber
74.125.18.80/29 lpp
74.125.18.144/29 grq
74.125.18.208/29 grq
etc
all listed on https://developers.google.com/speed/public-dns/faq
jlgaddis: yeh but i mean it's not even the same country
for me i think it's taiwan or hong kong or something
it's going to depend on the physical location of the client that the original request came from
for example, a client in taiwan using 8.8.8.8 is going to hit google's dns server in taiwan and so they're going to be querying your authoritative servers from taiwan
if i look at the query logs on my authoritative servers, i see lookups from all over the place (as expected)
yeh
but new zealand isn't near taiwan :/
actually it's closer than los angeles
bizzare
ping is higher to there though
i guess i'm missing something... what does NZ have to do with anything?
it's where i am
maybe some people are closer to the dns servers requests are made from
NZ shall forever be the land of LOTR to me
heh
anyway the point was that google isn't necessarily a good reference with tracerouting etc
cos their setup is more complicated, and sometimes hidden
also anycasted yea
and also doesn't have location information easily availble
like you can lokup where the google dns stuff comes from
but geoip database isn't accurate, and reverse lookups aren't obvious
or non-existant
heh, google uses the city tied to my ARIN POC record as the "location" for ip addresses allocated to us
even though i live a good distance away from where they're actually being used
(my personal address/po box is what's listed in my poc record, not the address of the company)
hmm all google addresses say california