reverse DNS question
Chris Gray
CGRAY at santa-clarita.com
Wed Aug 6 23:48:55 UTC 2003
OK, I understand the point of not top posting, so I've replied below...
=)
>A: Because people read from top to bottom.
>Q: Why is top posting bad?
>You seem to want to have PTR records for, say,
>193.192-222.136.165.64.in-addr.arpa, but in your zone file, you set
the
>value of $ORIGIN to 192.136.165.64.in-addr.arpa.
>Thus, the line
>193 PTR dns1.santa-clarita.com.
>gives you a PTR record for 193.192.136.165.64.in-addr.arpa., which is
>not what you want. Are you sure you followed PacBell's instructions
to
>the letter?
Actually, according to PacBell, and from the fact that it is now
working,
it doesn't seem work that way. Also, PacBell's directions were very
vague.
>-Pete
After trial-and-error testing using the information I received from the
list
and the correct zone name from PacBell, I have resolved our reverse
lookup problems. Below is the current zone and conf files.
Thanks to everyone for your replies!
Cheers!
Chris
[root at DNS1 master-zones]# cat 192.136.165.64.rev
$ttl 38400
192.136.165.64.in-addr.arpa. IN SOA DNS1.santa-clarita.com.
admin.santa-clarita.com. (
2003080602
10800
3600
604800
38400 )
192.136.165.64.in-addr.arpa. IN NS
DNS1.santa-clarita.com.
$ORIGIN 192.136.165.64.in-addr.arpa.
@ IN NS dns1.santa-clarita.com.
IN NS ns1.pbi.net
193 PTR dns1.santa-clarita.com.
194 PTR mail.santa-clarita.com.
195 PTR www.secure-santa-clarita.com.
198 PTR webcam1.santa-clarita.com.
199 PTR portal.santa-clarita.com.
200 PTR phoenix.santa-clarita.com.
201 PTR pegasus.santa-clarita.com.
205 PTR www.santa-clarita.com.
[root at DNS1 master-zones]#
---------------------------------------------------------
from named.conf
zone "192.136.165.64.in-addr.arpa" {
type master;
file "/var/named/master-zones/192.136.165.64.rev";
};
---------------------------------------------------------
More information about the bind-users
mailing list