 |  |
I've checked over your setup, and your primary server (dns1) is configured incorrectly. Your secondary server isn't configured at all for this zone, apparently.
Re: Lame delegation question
From: Men & Mice Support
Date: Wednesday, November 24, 1999
Time: 3:28:00 pm
To fix your primary server (dns1), do the following:
o In QuickDNS Pro Admin, open up your reverse zone file (99.58.195.in-addr.arpa.).
o From the Domain menu, select Domain Information.
o In the Name field, change it to this: "192/27.99.58.195.in-addr.arpa.". In other words, add "192/27." to the front of it.
o Close the dialog, save the file, and close it.
To fix your secondary server (dns2), do the following:
o In QuickDNS Pro Admin, select Secondary Data from the Window menu.
o In the resulting window, create a new record with the following values in the first three columns:
Domain Name: 192/27.99.58.195.in-addr.arpa.
Filename: 192/27.99.58.195.in-addr.arpa.
IP Address 1: 195.58.99.197
o Click the Save button.
Actually, the value of the "Filename" field can be any valid Mac filename you want, but giving it the same value as the "Domain Name" field is a good standard; this way, you never have to worry about duplicate names, and it makes AppleScripts easier to write.
Within a minute or two after each of the above procedures, the server in question will notice the change and update itself; you should see this reflected in the log window. After that, everything should be up and running on your end, so that when your ISP fixes their typo (dns instead of dns1), reverse lookups should work properly.
At 2:53 PM +0100 11/24/99, Petrus wrote:
>Sorry for this probably basic question, but here goes:
>
>My ISP delegated me a part of a class c-net so that I could be responsible
>for the reverse records :-)
>
>When I perform a DNS query I get the following result:
>
>------------------
>Query: 195.99.58.195.in-addr.arpa. Query type: PTR record
>Recursive query: Yes Authoritative answer: No
>Query time: 11331 ms. Server name: n/a
>
>Answer:
> 195.99.58.195.in-addr.arpa. 86400 CNAME 195.192/27.99.58.195.in-addr.arpa.
>
>Authority:
> 192/27.99.58.195.in-addr.arpa. 86400 NS dns.ior.nu.
> 192/27.99.58.195.in-addr.arpa. 86400 NS dns2.ior.nu.
>
>Additional:
> dns2.ior.nu. 74168 A 195.58.99.198
>------------------
>
>The first problem is that the authority is wrong, it should read dns1.ior.nu
>(instead of only dns.ior.nu). This I will speak to my ISP about.
>
>Second problem is that when I run the domain ior.nu through DNS Expert I get
>the following lame delegation error:
>
>------------------
>o Lame delegation received from "dns2.ior.nu." for
> "192/27.99.58.195.in-addr.arpa."
> The server "dns2.ior.nu." is listed as being authoritative for
> "192/27.99.58.195.in-addr.arpa.", but "dns2.ior.nu." does not
> contain authoritative data for the zone.
>------------------
>
>I suppose that it's the setup at my ISP that lists dns2.ior.nu as being
>"authoritative for 192/27.99.58.195.in-addr.arpa." since I've been delegated
>this part of the net.
>
>But how should I setup dns2.ior.nu to "contain authoritative data for the
>zone"?
>
>Many thanks,
>
>petrus
____________________________________________________________________
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