Re: localhost pitfall in resolver/solving Host or domain name not found. Name service error for name=localhost type=A: Host not found (also type=AAAA)

Does this help? Wietse smtp_dns_resolver_options (default: empty) DNS Resolver options for the Postfix SMTP client. Specify zero or more of the following options, separated by comma or whitespace. Option names are case-sensitive. Some options refer to domain

Re: localhost pitfall in resolver/solving Host or domain name not found. Name service error for name=localhost type=A: Host not found (also type=AAAA)

Am 05.05.2011 04:11, schrieb Matthias Andree: Now, possible workarounds: - be sure that /etc/resolv.conf contains a search list where at least one of the listed domains has a direct localhost resolving to 127.0.0.1 and/or ::1. Say, if you have search example.com another.example, at least

Re: localhost pitfall in resolver/solving Host or domain name not found. Name service error for name=localhost type=A: Host not found (also type=AAAA)

Am 05.05.2011 13:19, schrieb Wietse Venema: Does this help? Wietse smtp_dns_resolver_options (default: empty) DNS Resolver options for the Postfix SMTP client. Specify zero or more of the following options, separated by comma or whitespace. Option names

Re: localhost pitfall in resolver/solving Host or domain name not found. Name service error for name=localhost type=A: Host not found (also type=AAAA)

On Thu, May 05, 2011 at 03:49:35PM +0200, Matthias Andree wrote: Executive summary: We are facing a massive bug in the GNU glibc 2.11 and eglibc 2.13 resolvers which fails to even attempt a query for a name without dots if RES_DEFNAMES is unset. FreeBSD 8.2, DragonflyBSD 2.10 and Solaris

Re: localhost pitfall in resolver/solving Host or domain name not found. Name service error for name=localhost type=A: Host not found (also type=AAAA)

Am 05.05.2011 17:33, schrieb Victor Duchovni: On Thu, May 05, 2011 at 03:49:35PM +0200, Matthias Andree wrote: Executive summary: We are facing a massive bug in the GNU glibc 2.11 and eglibc 2.13 resolvers which fails to even attempt a query for a name without dots if RES_DEFNAMES is

Re: localhost pitfall in resolver/solving Host or domain name not found. Name service error for name=localhost type=A: Host not found (also type=AAAA)

On Thu, May 05, 2011 at 05:58:46PM +0200, Matthias Andree wrote: Do NOT use [localhost] as an SMTP nexthop. I always use [127.0.0.1]. If IPv6 works well for you, you can use [::1]. Hi Victor, Why do you recommend so, now that Postfix strips RES_DEFNAMES from _res.options by default?

Re: localhost pitfall in resolver/solving Host or domain name not found. Name service error for name=localhost type=A: Host not found (also type=AAAA)

Am 05.05.2011 18:23, schrieb Victor Duchovni: You know exactly what you mean when you use [localhost] as a nexthop, why not say so? What's the point of jumping through a pile of indirection and shared libraries just to arrive at an address that every administrator knows in advance. In fact,

Re: localhost pitfall in resolver/solving Host or domain name not found. Name service error for name=localhost type=A: Host not found (also type=AAAA)

On Thu, May 05, 2011 at 08:37:01PM +0200, Matthias Andree wrote: I had checked the Postfix 2.8 release notes immediately, but they bore no references to this particular HISTORY entry: It is in the 2.8 release notes: Major changes - dns lookup -- [Incompat 20100827]

Re: localhost pitfall in resolver/solving Host or domain name not found. Name service error for name=localhost type=A: Host not found (also type=AAAA)

Am 05.05.2011 20:46, schrieb Victor Duchovni: On Thu, May 05, 2011 at 08:37:01PM +0200, Matthias Andree wrote: I had checked the Postfix 2.8 release notes immediately, but they bore no references to this particular HISTORY entry: It is in the 2.8 release notes: Major changes - dns