Reverse problems

keith at mail.telestream.com keith at mail.telestream.com
Thu Jul 6 05:07:12 UTC 2000


Great process of deduction.  :-) 
It makes perfect sense to me. The b and t were the servers that Verio used
to have slaving us and then they jacked us around for a week or two while
they were "consolitading their name servers". At which point they told us
to change them to what they are currently. So looks like I need to request
that they get their ducks in a row and decide who they want to have truely
be the proper server.
Thanks again, there is a lesson for me in your deductive methods.  


Much appreciative.

Keith


=================================
Keith W.

At the helm <for better or worse>
=================================


On Thu, 6 Jul 2000, Tony Huang wrote:

> Keith,
> I finally get to know the full story.
> Let's start from the root server :
> -------------------------------------------
> dig ns @A.ROOT-SERVERS.NET 16.238.205.in-addr.arpa.
> 
> ; <<>> DiG 8.2 <<>> ns @A.ROOT-SERVERS.NET 16.238.205.in-addr.arpa.
> ; (1 server found)
> ;; res options: init recurs defnam dnsrch
> ;; got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> ;; flags: qr rd; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 3
> ;; QUERY SECTION:
> ;;      16.238.205.in-addr.arpa, type = NS, class = IN
> 
> ;; ANSWER SECTION:
> 16.238.205.in-addr.arpa.  6D IN NS  NS0.VERIO.NET.
> 16.238.205.in-addr.arpa.  6D IN NS  NS1.VERIO.NET.
> 16.238.205.in-addr.arpa.  6D IN NS  NS2.VERIO.NET.
> 
> ;; ADDITIONAL SECTION:
> NS0.VERIO.NET.          2D IN A         129.250.15.61
> NS1.VERIO.NET.          2D IN A         204.91.99.140
> NS2.VERIO.NET.          2D IN A         129.250.31.190
> ---------------------------------------------------------------------------------
> >From here we know ns0-2.verio.net are  authorative for zone
> 16.238.205.in-addr.arpa.
> Let's ask ns0.verio.net who is the name servers for this zone:
> --------------------------------------------------------------------------------
> dig ns @ns0.VERIO.NET 16.238.205.in-addr.arpa.
> 
> ; <<>> DiG 8.2 <<>> ns @ns0.VERIO.NET 16.238.205.in-addr.arpa.
> ; (1 server found)
> ;; res options: init recurs defnam dnsrch
> ;; got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> ;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
> ;; QUERY SECTION:
> ;;      16.238.205.in-addr.arpa, type = NS, class = IN
> 
> ;; ANSWER SECTION:
> 16.238.205.in-addr.arpa.  4H IN NS  b.ns.verio.net.
> 16.238.205.in-addr.arpa.  4H IN NS  t.ns.verio.net.
> 
> ;; ADDITIONAL SECTION:
> b.ns.verio.net.         1D IN A         129.250.35.32
> t.ns.verio.net.         1D IN A         192.67.14.16
> ------------------------------------------------------------------------------------
> 
> Then let's ask your name server who own this zone
> ------------------------------------------------------------------------------------
> 
> dig ns @ns.telestream.com 16.238.205.in-addr.arpa.
> 
> ; <<>> DiG 8.2 <<>> ns @ns.telestream.com 16.238.205.in-addr.arpa.
> ; (1 server found)
> ;; res options: init recurs defnam dnsrch
> ;; got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
> ;; QUERY SECTION:
> ;;      16.238.205.in-addr.arpa, type = NS, class = IN
> 
> ;; ANSWER SECTION:
> 16.238.205.in-addr.arpa.  4H IN NS  U.NS.VERIO.NET.
> 16.238.205.in-addr.arpa.  4H IN NS  C.NS.VERIO.NET.
> 
> ;; ADDITIONAL SECTION:
> U.NS.VERIO.NET.         12h50m50s IN A  192.67.14.17
> C.NS.VERIO.NET.         1d12h50m47s IN A  129.250.35.33
> ----------------------------------------------------------------------
> Obvious it is between you and your ISP.
> You can happily enjoy the reverse resolution between your name servers and  these
> two name servers namely (U.NS.VERIO.NET. C.NS.VERIO.NET.).
> The rest of world will query the root name servers for name resolution.
> Which goes to b.ns.verio.net. and t.ns.verio.net. and bad news is these two name
> servers knows nothing about 16.238.205.in-addr.arpa. :-(
> 
> What you have to do is chang you ns record accordingly and ask ISP to slave your
> zone on the right servers.
> 
> I just try to help, but really think I shouldn't humiliate myself in fornt of other
> dns administrators here. I will unsubscribe from this list. It last only one day
> :-(
> 
> Good luck!
> 
> 
> 
> 
> keith at mail.telestream.com wrote:
> 
> > Actually that's not the case here. We've had these /24's for nearly 4
> > years and this is the first instance of this. They are authorative for the
> > IP's and always have been. We control the files and put their name servers
> > in the NS sections and they just slave the files from us.
> > If you query both of the servers for an IP in either /24 they resolve
> > exactly as we have them setup, proving that they are pulling the proper
> > files and all is well. The question is why one of the /24's would not be
> > working if querying other name severs but the other would work. They are
> > both setup the same.
> > example:
> > Fist query my server, then the same IP on the server slaving our PTR's
> > then some remote server.
> >
> > # nslookup
> > Default Server:  ns.telestream.com
> > Address:  205.238.4.3
> >
> > > 205.238.16.154
> > Server:  ns.telestream.com
> > Address:  205.238.4.3
> >
> > Name:    x.angledetailing.com
> > Address:  205.238.16.154
> >
> > -----
> >
> > > server c.ns.verio.net
> > Default Server:  c.ns.verio.net
> > Address:  129.250.35.33
> >
> > > 205.238.16.154
> > Server:  c.ns.verio.net
> > Address:  129.250.35.33
> >
> > Name:    x.angledetailing.com
> > Address:  205.238.16.154
> >
> > -----
> >
> > > server hendrix.aa.net
> > Default Server:  hendrix.aa.net
> > Address:  204.157.220.4
> >
> > > 205.238.16.154
> > Server:  hendrix.aa.net
> > Address:  204.157.220.4
> >
> > *** hendrix.aa.net can't find 205.238.16.154: Server failed
> >
> > Keith
> >
> > =================================
> > Keith W.
> >
> > At the helm <for better or worse>
> > =================================
> >
> > On Wed, 5 Jul 2000, Tony Huang wrote:
> >
> > >
> > > Your ISP didn't delegate the zone to your name servers yet.
> > > dig ns @c.ns.VERIO.NET 16.238.205.in-addr.arpa.
> > >
> > > ; <<>> DiG 8.2 <<>> ns @c.ns.VERIO.NET 16.238.205.in-addr.arpa.
> > > ; (1 server found)
> > > ;; res options: init recurs defnam dnsrch
> > > ;; got answer:
> > > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> > > ;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
> > > ;; QUERY SECTION:
> > > ;;      16.238.205.in-addr.arpa, type = NS, class = IN
> > >
> > > ;; ANSWER SECTION:
> > > 16.238.205.in-addr.arpa.  4H IN NS  C.NS.VERIO.NET.
> > > 16.238.205.in-addr.arpa.  4H IN NS  U.NS.VERIO.NET.
> > >
> > > ;; ADDITIONAL SECTION:
> > > C.NS.VERIO.NET.         10h4m42s IN A   129.250.35.33
> > > U.NS.VERIO.NET.         10h4m42s IN A   192.67.14.17
> > >
> > > Joseph S D Yao wrote:
> > >
> > > > On Wed, Jul 05, 2000 at 03:23:07PM -0700, keith at mail.telestream.com wrote:
> > > > > I have two /24's that my upstream is pulling ptr's from us for.
> > > > > The problem is that one of the /24's will reverse just fine where the
> > > > > other will not if querying from any ns not associated with verio or
> > > > > myself. I'm curious if this could be a problem on my end or there
> > > > > end. Here is all the info. Hope this isn't to general a question.
> > > > >
> > > > > /24 #1     205.238.16/24
> > > > > /24 #2     205.238.4/24
> > > > >
> > > > > My name server  ns.telestream.com
> > > > > Upstream name servers  c.ns.verio.net   u.ns.verio.net
> > > > >
> > > > > If I do a reverse lookup on any IP in either /24 they work fine if
> > > > > querying my server or either of the verio ns servers. If using some other
> > > > > ns to query the 205.238.16/24, it fails where the 205.238.4/24's
> > > > > will work just fine.
> > > > > Any idea's where the problem may be? Thanks for any and all info.
> > > > > If I've not given enough info let me know.
> > > >
> > > > 16.238.205.in-addr.arpa nameserver = NS1.VERIO.NET
> > > > 16.238.205.in-addr.arpa nameserver = NS2.VERIO.NET
> > > > 16.238.205.in-addr.arpa nameserver = NS0.VERIO.NET
> > > >
> > > > 4.238.205.in-addr.arpa  nameserver = NS1.VERIO.NET
> > > > 4.238.205.in-addr.arpa  nameserver = NS2.VERIO.NET
> > > > 4.238.205.in-addr.arpa  nameserver = NS0.VERIO.NET
> > > >
> > > > *** No address information is available for "1.16.238.205.in-addr.arpa."
> > > >
> > > > 1.4.238.205.in-addr.arpa        name = router.telestream.com
> > > > 4.238.205.in-addr.arpa  nameserver = C.NS.VERIO.NET
> > > > 4.238.205.in-addr.arpa  nameserver = U.NS.VERIO.NET
> > > > C.NS.VERIO.NET  internet address = 129.250.35.33
> > > > U.NS.VERIO.NET  internet address = 192.67.14.17
> > > >
> > > > It looks like Verio has an inconsistency in its name server lists for
> > > > 4.238.205.in-addr.arpa.  Nevertheless, Verio has a reverse-DNS entry
> > > > for 1.4.238.205.in-addr.arpa.
> > > >
> > > > I have either picked a bad number for the 16.* network, or Verio does
> > > > not have it entered correctly - or, possibly, in the right name servers.
> > > >
> > > > Good luck.
> > > >
> > > > --
> > > > Joe Yao                         jsdy at cospo.osis.gov - Joseph S. D. Yao
> > > > COSPO/OSIS Computer Support                                     EMT-B
> > > > -----------------------------------------------------------------------
> > > > This message is not an official statement of COSPO policies.
> > >
> > >
> > >
> 




More information about the bind-users mailing list