Re: Reverse DNS fails with "cannot find your hostname" when forward IP is wrong
- Michael Monnerie:
> On Donnerstag 27 August 2009 Wietse Venema wrote:It is good to see that you have learned to read logfiles.
> > And this was logged when a reverse hostname resolved to the wrong IP
> > address:
> > ? ? Aug 26 00:26:12 spike postfix/smtpd: warning:
> > 188.8.131.52: address not listed for hostname
> > relay2nd.mail.sohu.com
> I just found a good logging example with the nfs server:
> rpc.mountd: Fake hostname ipmi-p4u.zmi.at for 184.108.40.206 - forward
> lookup doesn't exist
> That statement makes it clear, and would be a nice message for postfix
I think that the existing messages are adequate:
220.127.116.11: address not listed for hostname example.com
18.104.22.168: hostname example.com verification failed: Non-recoverable failure in name resolution
The "Non-recoverable failure in name resolution" portion is provided
by the system library; there are other reasons that might be logged
here instead. This text may not be as "pretty" as what you suggest,
but it is more precise than simplistically claiming "forward lookup
doesn't exist" (apart from the fact that the text is nonsensical).
If you had read the Postfix warning messages, then you would not
have lost time solving your DNS problem.