Reverse DNS on a /25 called 127-1?
Yann Sommer
dump at soultwins.com
Thu Apr 18 17:30:21 UTC 2002
Hello,
My new upstream provider from which I obtained 66.221.101.0/25 (
66.221.101.1 - 66.221.101.127) instructed me to set up reverse DNS as
following:
<quote>
We have reverse delegation setup with the info you provided.
Our NS will forward requests to your NS using this zone
"127-1.101.221.66.IN-ADDR.ARPA."
for example:
ns1.soultwins.com. = 10.127-1.101.221.66.IN-ADDR.ARPA.
ns2.soultwins.com. = 15.127-1.101.221.66.IN-ADDR.ARPA.
</quote>
So I went ahead and set up 127-1.101.221.66.in-addr.arpa. (as strange as
this sounded to me), as following:
<quote from master/127-1.101.221.66.in-addr.arpa>
$ttl 38400
$ORIGIN 127-1.101.221.66.in-addr.arpa.
@ IN SOA ns1.soultwins.com. hostmaster.soultwins.com. (
1689246702
10800
3600
604800
38400 )
IN NS ns1.soultwins.com.
IN NS ns2.soultwins.com.
1 IN PTR soultwins.com.
...
127 IN PTR 4911.soultwins.com.
</quote>
and the zone into my named.conf as following:
<quote named.conf>
zone "127-1.101.221.66.in-addr.arpa." {
type master;
file "master/127-1.101.221.66.in-addr.arpa";
notify yes;
};
</quote>
That said and done, HUP'ed bind and got the following results:
ns1# nslookup 66.221.101.1
18-Apr-2002 17:19:37.674 queries:
XX+/66.221.101.10/1.0.0.127.in-addr.arpa/PTR/IN
Server: localhost.soultwins.com
Address: 127.0.0.1
18-Apr-2002 17:19:37.675 queries:
XX+/66.221.101.10/1.101.221.66.in-addr.arpa/PTR/IN
18-Apr-2002 17:19:37.678 lame-servers: Lame server on
'1.101.221.66.in-addr.arpa' (in '101.221.66.IN-ADDR.ARPA'?):
[216.221.162.81].53 'NS.CIHOST.COM'
18-Apr-2002 17:19:37.688 lame-servers: Lame server on
'1.101.221.66.in-addr.arpa' (in '101.221.66.IN-ADDR.ARPA'?):
[216.221.162.111].53 'NS2.CIHOST.COM'
*** localhost.soultwins.com can't find 66.221.101.1: Server failed
18-Apr-2002 17:20:15.253 default: ns_forw:
query(1.101.221.66.in-addr.arpa) All possible A RR's lame
I tried numerous different ways, including calling the zone
0/25.101.221.66.in-addr.arpa which yielded the same results. Only if I
would call the zone 101.221.66.in-addr.arpa (and thus claiming the whole
/24 as mine), reverse DNS would locally resolve, but not populate across
the internet.
What am I missing, or any ideas as to what I've been doing wrong?
Thank you very much,
Yann
More information about the bind-users
mailing list