Client Side Operations
Submitted by wfms on Fri, 2006-04-21 14:23.
To find out which actual server is responding to your anycast queries, use the UNIX dig command, as in:
dig @prisoner.iana.org hostname.as112.net any
The response should look something like this:
;; ANSWER SECTION: $ORIGIN hostname.as112.net. @ 15S TXT "Internet Software Consortium, Inc." "Palo Alto, CA, USA" TXT "See http://as112.net/ for more information." NS blackhole-1.iana.org. NS blackhole-2.iana.org. SOA hazel.isc.org. hostmaster.isc.org. ( 2002050100 ; serial 1H ; refresh 10M ; retry 4w2d ; expiry 15S ) ; minimum
Where the SOA RR MNAME tells the host name of the answering anycast server, the SOA RR RNAME tells the e-mail address of the server's administrator, and some unordered TXT RR's tell other information which may be of interest. (Note: the whole response must fit in a 512 octet DNS/UDP datagram without depending on EDNS0 for slack.)
If one would like, one could also insert a geographic RR (LOC) to aid in future visualization projects, such as in this example:
$TTL 1W
@ IN SOA flo.gigafed.net. dns.ryouko.imsb.nrc.ca. (
1 ; serial number
1W ; refresh
1M ; retry
1W ; expire
1W ) ; negative caching TTL
NS blackhole-2.iana.org.
NS blackhole-1.iana.org.
TXT "See http://as112.net/ for more information."
TXT "Federal GigaPOP" "Ottawa, Canada"
LOC 45 25 0.000 N 75 42 0.000 W 80.00m 1m 10000m 10m
»
- Login to post comments
