Reverse lookup problem

[Barry Margolin]

In article <Pine.LNX.4.21.0002081731580.8204-100000 at ddx.a2000.nu>,
 <bind-list at ddx.a2000.nu> wrote:
>i have a really weird problem
>
>i run a nameserver ns.explainer.nl (193.172.72.200)
>and when i try to lookup some ip's :
>
>[root at ddx /root]# ndc restart
>new pid is 8230
>[root at ddx /root]# nslookup 193.172.72.1
>Server:  localhost
>Address:  127.0.0.1
>
>*** No address (A) records available for 193.172.72.1

172.193.in-addr.arpa is delegated to:

172.193.in-addr.arpa.	432000	NS	ns1.unisource.nl.
172.193.in-addr.arpa.	432000	NS	ns2.unisource.nl.
172.193.in-addr.arpa.	432000	NS	ns1.surfnet.nl.
172.193.in-addr.arpa.	432000	NS	ns.ripe.net.

ns1.surfnet.nl and ns1.unisource.nl claim that 72.172.193.in-addr.arpa is
delegated to:

72.172.193.in-addr.arpa.	86400	NS	ns.explainer.nl.
72.172.193.in-addr.arpa.	86400	NS	ns1.unisource.nl.

but ns.ripe.net doesn't know anything about this delegation.  In fact, it
doesn't seem to be configured as an authoritative server for
172.193.in-addr.arpa at all.

You need to get your ISP to straighten this mess out.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.