On Tue, 22 Oct 2013, John Hardin wrote:
On Tue, 22 Oct 2013, Dave Funk wrote:
On Tue, 22 Oct 2013, Kai Schaetzl wrote:
Webmaster DKDB wrote on Tue, 22 Oct 2013 08:08:01 +0200:
> dkdb.dk.37.66.77.in-addr.arpa
Probably because of this. This reverse DNS is not under an existing top-
level-domain and looks very much like a normal reverse lookup (and not
the
result). Have them set it to a real public hostname.
Kai
Kai,
.in-addr.arpa. -is- the official top-level dns zone for reverse map data.
Granted, but nobody should be setting the *forward* name of a host to
something in the in-addr.arpa domain, which is what appears to have been done
here.
Both Kai & I were talking about the DNS reverse-map data for that IP address,
I have no idea where you're getting "*forward* name" out of this discussion.
Any "bind" DNS admin worth their salt would recognize that
"dkdb.dk.37.66.77.in-addr.arpa"
result as a clear indication of a mistake in the DNS reverse map zone data for
that IP address. If you don't believe me, google for dns reverse map zone
missing dots, and you'll find pages like:
http://www.zytrax.com/books/dns/apa/dot.html
(look at the very last example on that page for this exact type of error).
If that DNS zone file had the missing dot, it would have mapped that
77.66.37.119 adder to the hostname dkdb.dk.
So all the OP's woes were caused by a careless DNS admin at his ISP.
Checking it now, they've fixed it.
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
