Weird reverse dns problem
Shadow Hawkins on Wednesday, 04 August 2004 10:10:58
Just set up a nameserver for my reverse dns(ns.ph-is.de), and now I get this:
$ dig +trace c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa
; <<>> DiG 9.2.4rc5 <<>> +trace c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa
;; global options: printcmd
. 106998 IN NS C.ROOT-SERVERS.NET.
. 106998 IN NS D.ROOT-SERVERS.NET.
. 106998 IN NS E.ROOT-SERVERS.NET.
. 106998 IN NS F.ROOT-SERVERS.NET.
. 106998 IN NS G.ROOT-SERVERS.NET.
. 106998 IN NS H.ROOT-SERVERS.NET.
. 106998 IN NS I.ROOT-SERVERS.NET.
. 106998 IN NS J.ROOT-SERVERS.NET.
. 106998 IN NS K.ROOT-SERVERS.NET.
. 106998 IN NS L.ROOT-SERVERS.NET.
. 106998 IN NS M.ROOT-SERVERS.NET.
. 106998 IN NS A.ROOT-SERVERS.NET.
. 106998 IN NS B.ROOT-SERVERS.NET.
;; Received 436 bytes from 217.20.115.1#53(217.20.115.1) in 2 ms
ip6.arpa. 172800 IN NS NS.RIPE.NET.
ip6.arpa. 172800 IN NS NS.APNIC.NET.
ip6.arpa. 172800 IN NS NS.ICANN.ORG.
ip6.arpa. 172800 IN NS TINNIE.ARIN.NET.
;; Received 198 bytes from 192.33.4.12#53(C.ROOT-SERVERS.NET) in 105 ms
2.1.8.f.6.0.1.0.0.2.ip6.arpa. 43200 IN NS ns2.sixxs.net.
2.1.8.f.6.0.1.0.0.2.ip6.arpa. 43200 IN NS ns3.sixxs.net.
2.1.8.f.6.0.1.0.0.2.ip6.arpa. 43200 IN NS ns1.sixxs.net.
;; Received 113 bytes from 2001:610:240:0:53::193#53(NS.RIPE.NET) in 34 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604800 IN NS ns.ph-is.de.
;; Received 75 bytes from 2001:7b8:3:1e:290:27ff:fe0c:5c5e#53(ns2.sixxs.net) in 51 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 5 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 2 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 3 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 13 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 2 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
;; Received 91 bytes from 62.80.105.196#53(ns.ph-is.de) in 1 ms
c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604597 IN NS ns.ph-is.de.
dig: Too many lookups
What's wrong with that? The zone looks like this:
$TTL 86400
$ORIGIN c.c.2.1.8.f.6.0.1.0.0.2.ip6.arpa
@INSOA ns1.ph-is.de. hostmaster.zakx.de. (
1978022515; Serial
10800; Refresh
3600; Retry
2419200; Expire
604800 ); Default TTL
IN NS ns1.ph-is.de.
IN NS ns2.ph-is.de.
IN NS ns3.ph-is.de.
IN NS ns4.ph-is.de.
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 IN PTR v6.zakx.de.
Thanks in advance,
Sven Gebhardt
Posting is only allowed when you are logged in. |