Reverse DNS problems, local hostnames replaced by those of UUNet
pancho at acadia.net
Sat Nov 13 09:45:02 UTC 1999
I help manage 2 name servers - p1.acadia.net and p3.acadia.net.
Our service is multi-homed with feeds provided by UUNet and Cable and Wireless.
Recently, some customers started complaining that they have been denied ftp
access to other sites, when they investigated they (found out/were told)
that we did not have reverse DNS working on our end. (not true).
I found out the IPs that the people were having trouble with resolved
correctly on most name servers, but on some I saw a completely different
host name for that IP. (126.96.36.199 is one of those addresses). As that is
a UUNet IP I asked AUTH03.NS.UU.NET for information on 188.8.131.52 and it
said that was host218.acadia.net:
It gets more complicated: our name server started caching the UUNet host
names for these IPs, as some folks on other services found out. I am
restarting named every few days to clear out these entries, though that is
not my ideal.
Now, we were supposed to be authoritative for our own addresses. We sent
some messages out to UUNet, but have not heard back. Am I correct in
thinking that they are no longer delegating the resolution to us? This is
causing us a great deal of difficulty. What do you folks suttest
Pancho Cole, webmaster and hostmaster for AcadiaNet
Work (207)664-3100 webmaster at acadia.net
More information about the bind-users