[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] More PTR problems with RAQ3
- Subject: [cobalt-users] More PTR problems with RAQ3
- From: "landonak " <landonak@xxxxxxxxxxxxxxxx>
- Date: Sat Feb 3 07:33:02 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
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.
Here are examples of my named.conf and the zone file.
---------
named.conf
---------
options {
directory "/etc/named";
allow-transfer { xxx.x.x.xxx; xxx.xx.xxx.xxx; };
};
zone "." { type hint; file "db.cache"; };
zone "192-26.xxx.xxx.xx.in-addr.arpa" { type master; file
"pri.192-26.xxx.xxx.xx.in-addr.arpa"; };
-------------------------------
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
;
; Do Not edit BIND db files directly.
; Use the administrative web user interface
; /admin/ -> Control Panel -> DNS Parameters
; Custom additions may be made by creating a file of the same name as this but
; with a; .include suffix. Click Save Changes in the DNS web interface and
;the inclusion will be made.
;
193 in ptr mydomain.com.
------------
Is this written correctly by the RAQ3 QUI?
I greatly appreciate any help!
Landon