 |  |
>From: "Men & Mice Support" <cbuxton@menandmice.com>
Re: Classless delegation stopped working
From: Peter Lalor
Date: Tuesday, September 26, 2000
Time: 1:52:34 pm
>
>At 6:04 PM -0700 9/23/00, Peter Lalor wrote:
>>Here's the background: The Class C from which we're doing this
>>delegation, 208.184.186.0 is from AboveNet, so they are
>>authoritative for it, hence the above.net NS records. They delegate
>>the reverse to ns.infoasis.com, our BIND server. The BIND server
>>slaves everything off our QDNS server, which is not a listed NS
>>because no clients should query it. Does that make it look at least
>>somewhat more correct?
>
>Hmm... I think maybe we're talking about different things.
>Communications breakdown.
>
>Let's go over this in detail, starting with the delegation.
>
>f.root-servers.net says:
>184.208.in-addr.arpa. NS ns.above.net.
>184.208.in-addr.arpa. NS ns3.above.net.
>
>ns.above.net says:
>186.184.208.in-addr.arpa. NS ns.above.net.
>186.184.208.in-addr.arpa. NS ns3.above.net.
>129.186.184.208.in-addr.arpa. CNAME 129.128/25.186.184.208.in-addr.arpa.
>128/25.186.184.208.in-addr.arpa. NS socrates.compuvar.com.
>
>So your reverse zone is delegated to socrates.compuvar.com. They
>should delegate this to more than one server, but its functional so
>long as socrates.compuvar.com never goes down.
Good so far. And this is the NS record that I changed to the
canonical name from it's IP address. This change actually made it
work again, but I'm going to go through this anyway, as it helps me
learn WTF.
>That name has the following A record:
>socrates.compuvar.com. A 209.101.164.2
>
>Note that this is not any of the three IP addresses you gave before,
>yet it's one of the servers listed in the registration record for
>your domain. What's going on here?
This is the NT server that hosts 128/25.186.184.208.in-addr.arpa.,
per your lookup above. It is the correct name for this server; the
only error was that I had entered it's IP address rather than the
canonical name.
>Furthermore, socrates.compuvar.com says:
>129.128/25.186.184.208.in-addr.arpa. PTR router.dsl-sl.mossy.com.
>
>This then is the PTR record for 208.184.186.129. You indicated that
>this is your NT-based DNS server, yet its name appears to indicate
>that this is a router. What's going on here?
No, 208.184.186.129 is one of the end users that
socrates.compuvar.com hosts 128/25.186.184.208.in-addr.arpa. It is in
fact a router, and not a name server.
>All in all, I don't see how the following servers are involved:
>206.40.74.2 (your QuickDNS Pro server)
Hosts all our zones, forward and reverse, for the purpose of having
QDNS's great UI.
>206.40.74.1 (your BIND server)
Does recursive lookups for clients and slaves all zones from QDNS.
Reverses delegated to this server from upstream.
>208.184.186.129 (your NT server)
This is a mistake. As we saw above, the NT server
socrates.compuvar.com is at 209.101.164.2. 208.184.186.129 is an end
user for which this DNS is authoritative for the reverse.
Thanks for all the help. Fixing the NS record for
socrates.compuvar.com fixed my problem and talking through the rest
made me feel (semi) sane again.
--
Peter Lalor Infoasis
plalor@infoasis.com http://www.infoasis.com/
"Where's my burrito?" -- Homer
Messages In This Thread:
Return to Digital Point Solutions' Home Page