[ Pobierz całość w formacie PDF ]
suckerpunch.movie.edu.
Of course, you can also do this from the command line, like so:
% nslookup -type=aaaa suckerpunch.movie.edu.
and
% nslookup 2001:db8:cafe:f9::d3
dig
The chief difference between nslookup and dig is that dig has no interactive mode: you
specify everything at the command line. And dig is smart enough in most cases to
differentiate between domain names and record types, so you can specify those in
whichever order you like. To query a name server other than the first one in resolv
.conf, type an @ followed by its domain name or IP address. As I mentioned earlier, if
you use a domain name that owns both AAAA and A records, recent versions of dig
will use the IPv6 address, so:
% dig @terminator.movie.edu. soa movie.edu.
has the same effect as
% dig @2001:db8:cafe:1::1 soa movie.edu.
To look up a AAAA record, just specify aaaa on the command line:
% dig aaaa suckerpunch.movie.edu.
dig | 35
or
% dig suckerpunch.movie.edu. aaaa
Either way, the output will look something like this:
; DiG 9.8.0 suckerpunch.movie.edu. aaaa
;; global options: +cmd
;; Got answer:
;; ->>HEADER
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 5
;; QUESTION SECTION:
;suckerpunch.movie.edu. IN AAAA
;; ANSWER SECTION:
suckerpunch.movie.edu. 86400 IN AAAA 2001:db8:cafe:f9::d3
;; AUTHORITY SECTION:
movie.edu. 86400 IN NS terminator.movie.edu.
movie.edu. 86400 IN NS wormhole.movie.edu.
;; ADDITIONAL SECTION:
terminator.movie.edu. 86400 IN A 192.249.249.1
terminator.movie.edu. 86400 IN AAAA 2001:db8:cafe:1::1
wormhole.movie.edu. 86400 IN A 192.249.249.3
wormhole.movie.edu. 86400 IN A 192.253.253.3
wormhole.movie.edu. 86400 IN AAAA 2001:db8:cafe:2::1
;; Query time: 3 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Mar 27 19:42:46 2011
;; MSG SIZE rcvd: 219
To reverse-map an IPv6 address, avail yourself of the handy -x command-line option,
which takes an IPv6 address (rather than its equivalent 34-label domain name) as an
argument:
% dig -x 2001:db8:cafe:f9::d3
One trick suggested by Owen DeLong, one of my technical reviewers, is to let dig do
the hard work of creating the 34-label owner name of an IPv6 PTR record for you. For
example, rather than laboriously typing the owner name that corresponds to
2620:0:930::400:933, you could simply run dig -x 2620:0:930::400:933:
% dig -x 2620:0:930::400:933
; DiG 9.6.0-APPLE-P2 -x 2620:0:930::400:933
;; global options: +cmd
;; Got answer:
;; ->>HEADER
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;3.3.9.0.0.0.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.3.9.0.0.0.0.0.0.2.6.2.ip6.arpa. IN PTR
...
36 | Chapter 5: Troubleshooting
Then copy the owner name from the line below ;; QUESTION SECTION and paste it into
your zone data file.
Like nslookup, dig digs the abbreviated form of the IPv6 address. If you want to do it
the hard way, you ll have to specify the PTR query type on the command line:
% dig ptr 3.d.0.0.0.0.0.0.0.0.0.0.0.0.0.0.9.f.0.0.e.f.a.c.8.b.d.0.1.0.0.2.ip6.arpa.
dig | 37
[ Pobierz całość w formacie PDF ]