[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] More PTR problems with RAQ3
- Subject: Re: [cobalt-users] More PTR problems with RAQ3
- From: "landonak " <landonak@xxxxxxxxxxxxxxxx>
- Date: Sat Feb 3 10:10:31 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Actually, if you'll notice my original email, I DO have a single PTR record at the end of that zone file for 193.
I'm stumped!
Landon
---------- Original Message ----------------------------------
From: "Gerald Waugh" <gerald@xxxxxxxxx>
Reply-To: "Gerald Waugh" <gerald@xxxxxxxxx>
Date: Sat, 3 Feb 2001 12:35:07 -0500
>"landonak " <landonak@xxxxxxxxxxxxxxxx> wrote
>> I use a RAQ3 for my primary DNS and the secondary DNS is provided by my ISP.
>My PTR records do not work for one of my IP blocks, a classless range
>xx.xxx.xxx.xxx /26. However, my PTR records work great for my other three full
>class C's. I'm wondering if this is a problem with my ISP possibly not following
>RFC2317 for delegating classless ranges or if it is a problem with the way the
>RAQ3 writes the zone files.
>>
>> Gerald had mentioned on this list that there was an error in writing
>named.conf (/ instead of -) and I have corrected this however nslookups continue
>to fail.
>> -------------------------------
>> pri.192-26.xxx.xxx.xx.addr.arpa
>> -------------------------------
>>
>> $TTL 86400
>> 192/26.xxx.xxx.xx.in-addr.arpa. IN SOA pri.nameserver.com.
>myname.emailaddress.com. (
>> 2001020223
>> 10800
>> 3600
>> 604800
>> 86400
>> )
>> 192/26.xxx.xxx.xx.in-addr.arpa. IN NS pri.nameserver.com.
>> 192/26.xxx.xxx.xx.in-addr.arpa. IN NS sec.nameserver.com.
>> ; End SOA Header
>> ;
>You have not defined any PTR records. There needs to be entries in
>194 in ptr domain-using-IP-194.
>195 in ptr domain-using-IP-195.
>196 in ptr domain-using-IP-196.
>197 in ptr domain-using-IP-197.
>
>Using the GUI you would insert a PTR record in the relevant domain's (one / IP)
>records.
>Then when you save, fix named.conf and check pri.192-26.xxx.xxx.xx.addr.arpa
>for the ptr records. They should be there!!!
>Gerald
>
>
>
>
>