|
Reverse DNS? How long?
![[us]](/s/countries/us.gif) Shadow Hawkins on Tuesday, 27 March 2012 00:59:26
How long does it generally take SixXS to instantiate reverse DNS for a routed subnet? First thing this morning I spec'd name servers for reverse DNS for a subdomain and as of about 7 hours later it hasn't shown up. If I dig -x @the_name_servers for the same v6 IP I get results, so I know that DNS is set up properly, and I also get results from a recursive lookup for boxes on other SixXS subnets I maintain, but this particular subnet doesn't seem to reverse-resolve yet on the larger Internet.
I'm not going to whinge to the contact address yet since this may resolve within 24 hours or so, but I'd hoped it would be up within a couple of hours.
Reverse DNS? How long?
DNS updates are pushed every 15 minutes, thus it should be there. Do note that DNS is a cached thing thus you might be requesting the cached answer.
For debugging the best suggestion is using something like:
$ dig +trace c.d.1.0.8.3.9.1.1.0.0.2.ip6.arpa
; <<>> DiG 9.8.1-P1 <<>> @8.8.8.8 +trace c.d.1.0.8.3.9.1.1.0.0.2.ip6.arpa
; (1 server found)
;; global options: +cmd
.23310INNSa.root-servers.net.
.23310INNSb.root-servers.net.
.23310INNSc.root-servers.net.
.23310INNSd.root-servers.net.
.23310INNSe.root-servers.net.
.23310INNSf.root-servers.net.
.23310INNSg.root-servers.net.
.23310INNSh.root-servers.net.
.23310INNSi.root-servers.net.
.23310INNSj.root-servers.net.
.23310INNSk.root-servers.net.
.23310INNSl.root-servers.net.
.23310INNSm.root-servers.net.
;; Received 228 bytes from 8.8.8.8#53(8.8.8.8) in 330 ms
ip6.arpa.172800INNSe.ip6-servers.arpa.
ip6.arpa.172800INNSf.ip6-servers.arpa.
ip6.arpa.172800INNSb.ip6-servers.arpa.
ip6.arpa.172800INNSa.ip6-servers.arpa.
ip6.arpa.172800INNSd.ip6-servers.arpa.
ip6.arpa.172800INNSc.ip6-servers.arpa.
;; Received 422 bytes from 2001:dc3::35#53(2001:dc3::35) in 150 ms
9.1.1.0.0.2.ip6.arpa.86400INNSu.arin.net.
9.1.1.0.0.2.ip6.arpa.86400INNSv.arin.net.
9.1.1.0.0.2.ip6.arpa.86400INNSw.arin.net.
9.1.1.0.0.2.ip6.arpa.86400INNSx.arin.net.
9.1.1.0.0.2.ip6.arpa.86400INNSz.arin.net.
9.1.1.0.0.2.ip6.arpa.86400INNSns2.lacnic.net.
9.1.1.0.0.2.ip6.arpa.86400INNSsec1.apnic.net.
9.1.1.0.0.2.ip6.arpa.86400INNSsec1.authdns.ripe.net.
9.1.1.0.0.2.ip6.arpa.86400INNSsec3.apnic.net.
;; Received 239 bytes from 2001:500:86::86#53(2001:500:86::86) in 1518 ms
8.3.9.1.1.0.0.2.ip6.arpa. 10800INNSNS2.PHX6.PUREGIG.NET.
8.3.9.1.1.0.0.2.ip6.arpa. 10800INNSNS1.PHX6.PUREGIG.NET.
;; Received 102 bytes from 202.12.28.140#53(202.12.28.140) in 262 ms
1.0.8.3.9.1.1.0.0.2.ip6.arpa. 86400 INNSns1.sixxs.net.
1.0.8.3.9.1.1.0.0.2.ip6.arpa. 86400 INNSns2.sixxs.net.
1.0.8.3.9.1.1.0.0.2.ip6.arpa. 86400 INNSns3.sixxs.net.
;; Received 113 bytes from 140.99.101.18#53(140.99.101.18) in 201 ms
c.d.1.0.8.3.9.1.1.0.0.2.ip6.arpa. 604800 IN NSns.fmp.com.
c.d.1.0.8.3.9.1.1.0.0.2.ip6.arpa. 604800 IN NSns2.fmp.com.
;; Received 124 bytes from 78.141.179.38#53(78.141.179.38) in 361 ms
c.d.1.0.8.3.9.1.1.0.0.2.ip6.arpa. 86400IN SOAfmp.com. fmouse.fmp.com. 2012031903 10800 900 604800 86400
;; Received 100 bytes from 208.81.244.105#53(208.81.244.105) in 126 ms
Then you see where the delegation breaks.
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 27 March 2012 11:44:37
Posting is only allowed when you are