Re: Confused about /24 in-addr.arpa NS delegation debug problem
In message <4d271802.5030...@gmail.com>, Gary Wallis writes: > Thanks guys for all the feedback. > > Yes seems like RIPE is involved, and The Planet (TP) refuses to fix > delegation or say they can't 'cause of RIPE, but sounds funny to me, and > I know that many TP tech support staffers know next to nil about DNS. RIPE and all the RIRs handle this sort of configuration all the time. If The Planet can't get this fixed for you then you really should find another ISP. This is DNS basics and if your ISP can't handle talking to the RIR to get you nameservers registered instead of theirs then what else are they going to get wrong? Mark > Have fun with DNS in 2011. Cheers! > Gary > ___ > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Confused about /24 in-addr.arpa NS delegation debug problem
Thanks guys for all the feedback. Yes seems like RIPE is involved, and The Planet (TP) refuses to fix delegation or say they can't 'cause of RIPE, but sounds funny to me, and I know that many TP tech support staffers know next to nil about DNS. Have fun with DNS in 2011. Cheers! Gary ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Confused about /24 in-addr.arpa NS delegation debug problem
> Phil Mayers writes: >> Delegation nameservers above differ from nameservers in-zone below >>> >>> 147.95.81.in-addr.arpa. 86400 IN NS ns2.callingcloud.net. >>> 147.95.81.in-addr.arpa. 86400 IN NS ns1.callingcloud.net. >>> ;; Received 96 bytes from 207.218.247.135#53(ns1.theplanet.com) in >>> 106 ms On 07.01.11 09:19, p...@mail.nsbeta.info wrote: > What problems will be caused due to this case? if all of those nameservers will provide the same answers, none. However, if any of them breaks, you will have strange problems appearing ocasionally on different resursive servers. so, better point NS to correct nameservers in both delegation and zone itself. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. BSE = Mad Cow Desease ... BSA = Mad Software Producents Desease ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Confused about /24 in-addr.arpa NS delegation debug problem
In message <4d26508c.7090...@gmail.com>, Gary Wallis writes: > (Some dig output lines deleted to keep short) > > Why does this not work (but below next dig with +trace seems to imply > that it should?): More modern version of dig report the error "BAD (HORIZONTAL) REFERRAL". If 147.95.81.in-addr.arpa is delegated to ns?.ltheplanet.com when it should be delegated to ns?.callingcloud.net. Your ISP has to update the nameserver information held by RIPE. Mark 147.95.81.in-addr.arpa. 172800 IN NS ns1.theplanet.com. 147.95.81.in-addr.arpa. 172800 IN NS ns2.theplanet.com. ;; Received 115 bytes from 2001:610:240:0:53::3#53(ns-pri.ripe.net) in 739 ms 147.95.81.in-addr.arpa. 86400 IN NS ns2.callingcloud.net. 147.95.81.in-addr.arpa. 86400 IN NS ns1.callingcloud.net. ;; BAD (HORIZONTAL) REFERRAL ;; Received 96 bytes from 207.218.223.162#53(ns2.theplanet.com) in 206 ms 100.147.95.81.in-addr.arpa. 86400 INPTR ns3.callingcloud.net. 147.95.81.in-addr.arpa. 86400 IN NS ns3.callingcloud.net. 147.95.81.in-addr.arpa. 86400 IN NS ns1.callingcloud.net. 147.95.81.in-addr.arpa. 86400 IN NS ns2.callingcloud.net. ;; Received 176 bytes from 174.121.136.100#53(ns1.callingcloud.net) in 215 ms > [r...@web0 /]# dig -x 81.95.147.100 > > ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> -x 81.95.147.100 > ;; global options: printcmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 10895 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;100.147.95.81.in-addr.arpa.IN PTR > > ;; Query time: 489 msec > ;; SERVER: 8.8.4.4#53(8.8.4.4) > ;; WHEN: Fri Jan 7 02:20:28 2011 > ;; MSG SIZE rcvd: 44 > > But this returns the PTR: (WTF?) > > [r...@web0 /]# dig -x 81.95.147.100 +trace > > ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> -x 81.95.147.100 +trace > ;; global options: printcmd > . 80166 IN NS j.root-servers.net. > . 80166 IN NS i.root-servers.net. > ...snip > . 80166 IN NS b.root-servers.net. > ;; Received 228 bytes from 8.8.8.8#53(8.8.8.8) in 83 ms > > arpa. 172800 IN NS f.root-servers.net. > arpa. 172800 IN NS b.root-servers.net. > ...snip > arpa. 172800 IN NS e.root-servers.net. > ;; Received 508 bytes from 192.58.128.30#53(j.root-servers.net) in 165 ms > > 81.in-addr.arpa.86400 IN NS SEC1.APNIC.NET. > 81.in-addr.arpa.86400 IN NS SEC3.APNIC.NET. > 81.in-addr.arpa.86400 IN NS NS3.NIC.FR. > 81.in-addr.arpa.86400 IN NS NS-PRI.RIPE.NET. > 81.in-addr.arpa.86400 IN NS TINNIE.ARIN.NET. > 81.in-addr.arpa.86400 IN NS SNS-PB.ISC.ORG. > 81.in-addr.arpa.86400 IN NS SUNIC.SUNET.SE. > ;; Received 223 bytes from 192.5.5.241#53(f.root-servers.net) in 166 ms > > 147.95.81.in-addr.arpa. 172800 IN NS ns1.theplanet.com. > 147.95.81.in-addr.arpa. 172800 IN NS ns2.theplanet.com. > ;; Received 93 bytes from 202.12.29.59#53(SEC1.APNIC.NET) in 317 ms > > 147.95.81.in-addr.arpa. 86400 IN NS ns2.callingcloud.net. > 147.95.81.in-addr.arpa. 86400 IN NS ns1.callingcloud.net. > ;; Received 96 bytes from 207.218.247.135#53(ns1.theplanet.com) in 106 ms > > 100.147.95.81.in-addr.arpa. 86400 INPTR ns3.callingcloud.net. > 147.95.81.in-addr.arpa. 86400 IN NS ns1.callingcloud.net. > 147.95.81.in-addr.arpa. 86400 IN NS ns2.callingcloud.net. > 147.95.81.in-addr.arpa. 86400 IN NS ns3.callingcloud.net. > ;; Received 176 bytes from 174.121.136.101#53(ns2.callingcloud.net) in > 106 ms > > > The Planet (now SoftLayer) supposedly has setup straight class C > delegation to ns1/2.callingcloud.net > > What am I missing here? What dig command can point to the delegation > problem? > > > Thanks for any advice, hints or even the bloody answer. > > > --- > PD > > The ns1/3 NSs work as expected: > > [r...@web0 /]# dig @ns1.callingcloud.net -x 81.95.147.100 +short > ns3.callingcloud.net. > [r...@web0 /]# dig @ns2.callingcloud.net -x 81.95.147.100 +short > ns3.callingcloud.net. > [r...@web0 /]# dig @ns3.callingcloud.net -x 81.95.147.100 +short > ns3.callingcloud.net. > > > ___ > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Confused about /24 in-addr.arpa NS delegation debug problem
Phil Mayers writes: Delegation nameservers above differ from nameservers in-zone below 147.95.81.in-addr.arpa. 86400 IN NS ns2.callingcloud.net. 147.95.81.in-addr.arpa. 86400 IN NS ns1.callingcloud.net. ;; Received 96 bytes from 207.218.247.135#53(ns1.theplanet.com) in 106 ms What problems will be caused due to this case? Thanks. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Confused about /24 in-addr.arpa NS delegation debug problem
On 01/06/2011 11:30 PM, Gary Wallis wrote: (Some dig output lines deleted to keep short) Why does this not work (but below next dig with +trace seems to imply that it should?): The delegation looks invalid: 147.95.81.in-addr.arpa. 172800 IN NS ns1.theplanet.com. 147.95.81.in-addr.arpa. 172800 IN NS ns2.theplanet.com. ;; Received 93 bytes from 202.12.29.59#53(SEC1.APNIC.NET) in 317 ms Delegation nameservers above differ from nameservers in-zone below 147.95.81.in-addr.arpa. 86400 IN NS ns2.callingcloud.net. 147.95.81.in-addr.arpa. 86400 IN NS ns1.callingcloud.net. ;; Received 96 bytes from 207.218.247.135#53(ns1.theplanet.com) in 106 ms ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Confused about /24 in-addr.arpa NS delegation debug problem
(Some dig output lines deleted to keep short) Why does this not work (but below next dig with +trace seems to imply that it should?): [r...@web0 /]# dig -x 81.95.147.100 ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> -x 81.95.147.100 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 10895 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;100.147.95.81.in-addr.arpa.IN PTR ;; Query time: 489 msec ;; SERVER: 8.8.4.4#53(8.8.4.4) ;; WHEN: Fri Jan 7 02:20:28 2011 ;; MSG SIZE rcvd: 44 But this returns the PTR: (WTF?) [r...@web0 /]# dig -x 81.95.147.100 +trace ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> -x 81.95.147.100 +trace ;; global options: printcmd . 80166 IN NS j.root-servers.net. . 80166 IN NS i.root-servers.net. ...snip . 80166 IN NS b.root-servers.net. ;; Received 228 bytes from 8.8.8.8#53(8.8.8.8) in 83 ms arpa. 172800 IN NS f.root-servers.net. arpa. 172800 IN NS b.root-servers.net. ...snip arpa. 172800 IN NS e.root-servers.net. ;; Received 508 bytes from 192.58.128.30#53(j.root-servers.net) in 165 ms 81.in-addr.arpa.86400 IN NS SEC1.APNIC.NET. 81.in-addr.arpa.86400 IN NS SEC3.APNIC.NET. 81.in-addr.arpa.86400 IN NS NS3.NIC.FR. 81.in-addr.arpa.86400 IN NS NS-PRI.RIPE.NET. 81.in-addr.arpa.86400 IN NS TINNIE.ARIN.NET. 81.in-addr.arpa.86400 IN NS SNS-PB.ISC.ORG. 81.in-addr.arpa.86400 IN NS SUNIC.SUNET.SE. ;; Received 223 bytes from 192.5.5.241#53(f.root-servers.net) in 166 ms 147.95.81.in-addr.arpa. 172800 IN NS ns1.theplanet.com. 147.95.81.in-addr.arpa. 172800 IN NS ns2.theplanet.com. ;; Received 93 bytes from 202.12.29.59#53(SEC1.APNIC.NET) in 317 ms 147.95.81.in-addr.arpa. 86400 IN NS ns2.callingcloud.net. 147.95.81.in-addr.arpa. 86400 IN NS ns1.callingcloud.net. ;; Received 96 bytes from 207.218.247.135#53(ns1.theplanet.com) in 106 ms 100.147.95.81.in-addr.arpa. 86400 INPTR ns3.callingcloud.net. 147.95.81.in-addr.arpa. 86400 IN NS ns1.callingcloud.net. 147.95.81.in-addr.arpa. 86400 IN NS ns2.callingcloud.net. 147.95.81.in-addr.arpa. 86400 IN NS ns3.callingcloud.net. ;; Received 176 bytes from 174.121.136.101#53(ns2.callingcloud.net) in 106 ms The Planet (now SoftLayer) supposedly has setup straight class C delegation to ns1/2.callingcloud.net What am I missing here? What dig command can point to the delegation problem? Thanks for any advice, hints or even the bloody answer. --- PD The ns1/3 NSs work as expected: [r...@web0 /]# dig @ns1.callingcloud.net -x 81.95.147.100 +short ns3.callingcloud.net. [r...@web0 /]# dig @ns2.callingcloud.net -x 81.95.147.100 +short ns3.callingcloud.net. [r...@web0 /]# dig @ns3.callingcloud.net -x 81.95.147.100 +short ns3.callingcloud.net. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users