On Wed, Apr 29, 2015 at 09:33:29PM -0400, James B. Byrne wrote:
> >> > Looks as if your resolver is appending the search path to unknown
> >> > domains.
> >>
> >> Yes, I sort of gathered that. The questions I have are:
> >>
> >> Is it a defect?
> >> Is it a Postfix issue?
> >> Is it due to configuration or misconfiguration?
> >
> > What operating system are you using?
>
> CentOS-6.6 (RHEL6 respin)
This is not known to mishandle Postfix requests to the system
resolver.
It is rather more likely that the lookups you observed were from
the code that attempts to map the client's IP address to a name
and back. Those do use default search paths.
133.201.62.95.in-addr.arpa. IN PTR
static-133-201-62-95.ipcom.comunitel.net.
; <<>> DiG 9.10.1-P1 <<>> -t any static-133-201-62-95.ipcom.comunitel.net.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 231
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
The fact that the same name fails HELO checks (which don't use the
default suffixes) is not unexpected.
--
Viktor.
