reverse lookup for single address
Kevin Darcy
kcd at daimlerchrysler.com
Fri Sep 10 23:57:10 UTC 2004
You seem to be making this more confusing than is necessary. There are
really only 2 different possibilities here:
1) Your ISP has reverse records for 12.34.56.78, 12.34.56.80 and any/all
other addresses in that range that you care about, in the
56.34.12.in-addr.arpa zone. In this case, you don't need any
"redirection" since you can resolve these reverse records from your ISP.
For redundancy, you might want to set yourself up as a slave, or
2) Your ISP is missing 1 or more of the records you care about in its
56.34.12.in-addr.arpa zone. "Redirection" doesn't help you here since
your ISP doesn't have the records you want. You could either persuade
your ISP to add records for that/those address(es), or set each on up
selectively as master zones (e.g. 80.56.34.12.in-addr.arpa) on your own
server, but then you're stuck maintaining them. Another option would be
to set up 56.34.12.in-addr.arpa as a master zone on your nameserver,
thus "overriding" the version of that zone from the point of view of
anyone explicitly using your nameserver, but then you'd have to maintain
*all* of the records in that zone -- you'd never query your ISP for any
reverse records in that range.
- Kevin
Tony Tung wrote:
>Hi,
>
>But since 12.34.56.80 does not belong to me, is there a way I can=20
>redirect the request up to my ISP?
>
>Thanks,
>Tony
>
>On Sep 9, 2004, at 7:37 AM, Willy LR wrote:
>
>
>
>>Hi
>>
>>Seems like you have no PTR record for 12.34.56.80
>>
>>Just add it to your reverse zone file
>>
>>You can also automatically generate PTR records :
>>
>>$GENERATE 1-80 $.56.34.12.in-addr-arpa PTR host$.yourdomain.org
>>
>>Hope that helps
>>
>>Regards
>>
>>
>>
>>>De=A0: Tony Tung <tonytung at csua.berkeley.edu>
>>>Soci=E9t=E9=A0: ...
>>>Groupes de discussion=A0: comp.protocols.dns.bind
>>>Date=A0: Wed, 8 Sep 2004 19:17:32 +0000 (UTC)
>>>=C0=A0: comp-protocols-dns-bind at isc.org
>>>Objet=A0: reverse lookup for single address
>>>
>>>Hi,
>>>
>>>I'm trying to get my name server on my server to answer reverse=20
>>>lookup.
>>>That is, my server lives at 12.34.56.78 (address faked), but that is=20=
>>>
>>>
>
>
>
>>>the
>>>only address I have. I want to be able to do this from a remote=20
>>>server:
>>>
>>>nslookup 12.34.56.78 12.34.56.78
>>>
>>>and get a correct resolution. I've managed to do that much. =20
>>>However, I
>>>can no longer reverse-resolve other addresses in the same subnet from=20=
>>>
>>>
>
>
>
>>>my
>>>own server, i.e., I cannot reverse-map 12.34.56.80.
>>>
>>>Can someone give me some tips? This is what I have in my named.conf:
>>>
>>>zone "56.34.12.in-addr.arpa" IN {
>>> type slave;
>>> file "master/pub.rev";
>>> masters {
>>> 64.81.79.2;
>>> 216.231.41.2;
>>> };
>>>};
>>>
>>>and in pub.rev:
>>>
>>>$ORIGIN 56.34.12.in-addr.arpa.
>>>$TTL 3600
>>>@ IN SOA
>>>myserver.org. root.myserver.org. (
>>> 20030406 ; Serial
>>> 3600 ; Refresh
>>> 900 ; Retry
>>> 3600000 ; Expire
>>> 3600 ) ; Minimum
>>> IN NS myserver.org.
>>>78 IN PTR myserver.org.
>>>
>>>
>>>Thanks!
>>>Tony
>>>
>>>
>>>
>>>
>>
>>
>
>
>
>
>
>
>
More information about the bind-users
mailing list