Andreas 'ads' Scherbaum wrote:
> On Tue, 06 Nov 2007 17:37:18 -0400 Marc G. Fournier wrote:
>
>> - --On Tuesday, November 06, 2007 21:33:08 +0100 Magnus Hagander
>> <magnus@hagander.net> wrote:
>>
>>> Marc G. Fournier wrote:
>>>> 'k, I'm confused ... the only name that should be referenced in any config
>>>> file is maia.hub.org, which breaks down as:
>>>>
>>>> Name: maia.hub.org
>>>> Address: 200.46.204.184
>>>> Name: maia.hub.org
>>>> Address: 200.46.204.183
>>>>
>>>> So, how/where are ppl seeing 200.46.204.187 :(
>>> dig -x 200.46.204.187
>>>
>>> returns
>>> 187.204.46.200.in-addr.arpa. 18000 IN PTR maia-2.hub.org.
>>>
>>> Similar for -1.
>> Right, and?
>
> ads@iridium:/home/ads > dig -x maia-2.hub.org.
> dig: '.org.hub.maia-2.in-addr.arpa.' is not a legal name (empty label)
-x implies a reverse/PTR lookup so you need to supply an ip-address ...
>
>
> And where this came from?
>
> Nov 1 20:30:53 base postfix/smtpd[11763]: warning: smtpd_peer_init: 200.46.204.187: address not listed for hostname
maia-2.hub.org
> Nov 1 20:30:54 base postfix/smtpd[11763]: NOQUEUE: reject: RCPT from unknown[200.46.204.187]: 450 <maia-2.hub.org>:
Helocommand rejected: Host not found; from=<pgsql-committers-owner+M30281@postgresql.org> to=<adsmail@wars-nicht.de>
proto=ESMTPhelo=<maia-2.hub.org>
>
> a) the ip-address has an invalid (missing) ptr record
> b) this server is knowing itself by maia-2.hub.org, which cannot resolved
> (but matches the invalid ptr record)
well this problem (200.46.204.187 having a PTR of maia-2.hub.org but
forward resolution is not correct/missing) seems to be fixed now (and
you log entry is now nearly a week old)
Stefan