Search Again:

Re: Create Reverse Zone

From: Men & Mice Support
Date: Tuesday, July 11, 2000
Time: 5:06:09 am

>> No problem. Presumably, you'd host this on both servers anyway, just
>> like your domain zones.
>
>I'll need to add details for the reverse zone in my secondary files on
>oxford.ldml.com wont I? What do I need to add here,
>"176-28.39.219.213.in-addr.arpa" as the domain name?

Exactly.

>> His delegation to your server won't
>> do much good, since the parent zone isn't delegated to him. He needs
>> to fix this; the whole 219.213.in-addr.arpa. zone isn't delegated
>> from ns.ripe.net.
>
>Oh goodie. That'll be fun to get sorted (NOT).
>
>How do you check this?

With DNS Expert's DNS query tool, or with any other such utility. DNS
Expert formats the output (and the input options) nicely.

Start by querying a root server, such as f.root-servers.net:
213.in-addr.arpa. NS ns.ripe.net.
213.in-addr.arpa. NS ns.eu.net.
213.in-addr.arpa. NS auth00.ns.uu.net.
213.in-addr.arpa. NS ns3.nic.fr.
213.in-addr.arpa. NS sunic.sunet.se.
213.in-addr.arpa. NS munnari.oz.au.
213.in-addr.arpa. NS ns.apnic.net.
213.in-addr.arpa. NS svc00.apnic.net.

Then follow up by querying one of these servers, such as ns.ripe.net:
213.in-addr.arpa. NS ns.ripe.net.
213.in-addr.arpa. NS ns.eu.net.
213.in-addr.arpa. NS auth00.ns.uu.net.
213.in-addr.arpa. NS ns3.nic.fr.
213.in-addr.arpa. NS sunic.sunet.se.
213.in-addr.arpa. NS munnari.oz.au.
213.in-addr.arpa. NS ns.apnic.net.
213.in-addr.arpa. NS svc01.apnic.net.

Note that it agrees with the root server. When it's queried for
219.213.in-addr.arpa, though, it gives an SOA record for
213.in-addr.arpa. This indicates that, while it is authoritative for
the parent zone, it has no record of this zone (219.213.in-addr.arpa).

Querying for 39.219.213.in-addr.arpa gives a simpler, more direct way
of saying there's no such beast. DNS Expert displays it as:
The host or domain "39.219.213.in-addr.arpa." does not exist

One of these latter two queries should lead to delegation records
pointing to your co-lo provider.

>> oxford.ldml.com isn't responding at all. Maybe that's the problem...?
>> Or are you working on it right now?
>
>Should be. Problem is that QDNS Pro its not picking up the secondary data so
>doesn't have anything to respond with. You should be able to ping it on
>213.219.39.178. QDNS Pro is running OK.

Yes, I can ping it. No, I can't get a response to a DNS query from it.

It should respond indicating that it doesn't know the answer, since
it hasn't yet pulled a copy of the zone.

Are you sure that QuickDNS Pro Server, and not Admin, is currently
running on it?
____________________________________________________________________
Chris Buxton cbuxton@menandmice.com
Men & Mice http://www.menandmice.com
Makers of: QuickDNS Pro



Messages In This Thread:



Return to Digital Point Solutions' Home Page