digでさー

前回も逆引きに触れましたけど、今回も逆引きのお話ですが、digのtraceというオプションでこんな結果になりました

C:\ >dig -x 59.106.187.94 +trace

; <<>> DiG 9.3.2 <<>> -x 59.106.187.94 +trace
;; global options: printcmd
. 224158 IN NS f.root-servers.net.
. 224158 IN NS h.root-servers.net.
. 224158 IN NS j.root-servers.net.
. 224158 IN NS k.root-servers.net.
. 224158 IN NS e.root-servers.net.
. 224158 IN NS b.root-servers.net.
. 224158 IN NS i.root-servers.net.
. 224158 IN NS a.root-servers.net.
. 224158 IN NS g.root-servers.net.
. 224158 IN NS m.root-servers.net.
. 224158 IN NS c.root-servers.net.
. 224158 IN NS d.root-servers.net.
. 224158 IN NS l.root-servers.net.
;; Received 512 bytes from 192.168.24.1#53(192.168.24.1) in 18 ms

in-addr.arpa. 172800 IN NS c.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS e.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS f.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS a.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS b.in-addr-servers.arpa.
in-addr.arpa. 172800 IN NS d.in-addr-servers.arpa.
;; Received 420 bytes from 192.5.5.241#53(f.root-servers.net) in 62 ms

59.in-addr.arpa. 86400 IN NS ns1.apnic.net.
59.in-addr.arpa. 86400 IN NS ns2.lacnic.net.
59.in-addr.arpa. 86400 IN NS ns3.apnic.net.
59.in-addr.arpa. 86400 IN NS ns4.apnic.net.
59.in-addr.arpa. 86400 IN NS sec1.authdns.ripe.net.
59.in-addr.arpa. 86400 IN NS apnic1.dnsnode.net.
59.in-addr.arpa. 86400 IN NS tinnie.arin.net.
;; Received 219 bytes from 196.216.169.10#53(c.in-addr-servers.arpa) in 468 ms

187.106.59.in-addr.arpa. 86400 IN NS ns1.dns.ne.jp.
187.106.59.in-addr.arpa. 86400 IN NS ns2.dns.ne.jp.
;; Received 89 bytes from 202.12.29.25#53(ns1.apnic.net) in 225 ms

94.187.106.59.in-addr.arpa. 3600 IN PTR vincentina.net.
187.106.59.in-addr.arpa. 3600 IN NS ns1.dns.ne.jp.
187.106.59.in-addr.arpa. 3600 IN NS ns2.dns.ne.jp.
;; Received 117 bytes from 210.188.224.9#53(ns1.dns.ne.jp) in 16 ms

やっぱ逆引きだと　ns1.vincentina.net　はちゃんと動いてないみたいです。

Related Posts

• PHPのアップデートをいそげ～
• 性能の違いが戦力の決定的差でない、ストレージ編・後編
• たけけんのネームサーバーメモ その弐 補足