Reverse DNS on non-network .0 addresses
McNutt, Justin M.
McNuttJ at missouri.edu
Thu Jan 31 15:52:04 UTC 2002
> Thanks for the quick reply!
No problem . :-)
> Here is the other relevant information in this situation:
>=20
> 66.153.40.0/22
>=20
> The zone I am doing reverse on:
> zone "42.153.66.in-addr.arpa"{ type master; file "66.153.42";
> allow-transfer{ 66.153.40.5; }; allow-update{ none;};};
>=20
> @ IN SOA ns.a1com.net. =20
> hostmaster.a1com.net. (
> 2002013102 ; serial
> 86400 ; refresh
> 3600 ; retry
> 3600000 ; expire
> 604800 ; default_ttl
> )
> @ IN NS ns.a1com.net.
> @ IN NS ns2.a1com.net.
> 0 IN PTR reverse.domain.com.
Nothing I see here shows a problem (your PTR is correct, your SOA is =
correct), which leaves a few possibilities:
1) There is an $origin directive between the NS records you show and =
the 0 record that is changing the name.
2) There is another record for 0.42.153.66.in-addr.arpa somewhere that =
is screwing up this one.
3) There is a problem with your name server itself that is rejecting =
this record (logs?).
If this helps, this is how we accomplished the 'zero' record:
;;;
$ttl 604800
@ IN SOA noc.missouri.edu. register.lists.missouri.edu. (
2002012502 ; Serial
7200 ; Refresh
3600 ; Retry
604800 ; Expire
86400 ; Minimum TTL
)
in ns noc.missouri.edu.
in ns ns3.missouri.edu.
;
$origin 93.206.128.in-addr.arpa.
;
0 in ptr mu-093000.dhcp.missouri.edu.
1 in ptr mu-093001.dhcp.missouri.edu.
(etc.)
--J
More information about the bind-users
mailing list