Re: Name service error for name=* type=AAAA, when it should be IPv4

2017-03-23 Thread chaouche yacine
On Wednesday, March 22, 2017 9:27 PM, Bastian Blank wrote: >- You run Postfix daemons chrooted? (check the chroot column in > /etc/postfix/master.cf) > >Bastian Nicely spotted. -- Yassine

Re: Name service error for name=* type=AAAA, when it should be IPv4

2017-03-22 Thread Marvin Renich
* Bastian Blank [170322 16:27]: > On Wed, Mar 22, 2017 at 04:11:19PM -0400, Marvin Renich wrote: > > At 12:30 I edited main.cf to add inet_protocols = ipv4, then restarted > > Postfix. I did not reboot or restart any other services, or (knowingly)

Re: Name service error for name=* type=AAAA, when it should be IPv4

2017-03-22 Thread Marvin Renich
* Bastian Blank [170322 15:09]: > Moin > > On Wed, Mar 22, 2017 at 01:04:36PM -0400, Marvin Renich wrote: > > Mar 21 14:42:45 basil postfix/smtp[12587]: 3AF35240229: > > to=, relay=none, delay=0.47, > >

Re: Name service error for name=* type=AAAA, when it should be IPv4

2017-03-22 Thread Bastian Blank
On Wed, Mar 22, 2017 at 04:11:19PM -0400, Marvin Renich wrote: > At 12:30 I edited main.cf to add inet_protocols = ipv4, then restarted > Postfix. I did not reboot or restart any other services, or (knowingly) > clear any dns cache. - You have by any chance a nameserver != 127.0.0.1 or ::1 in

Re: Name service error for name=* type=AAAA, when it should be IPv4

2017-03-22 Thread Marvin Renich
* Noel Jones [170322 14:38]: > On 3/22/2017 1:08 PM, Marvin Renich wrote: > > Thanks, Wietse and Noel. Once the IPv4 delivery fails for some reason, > > and Postfix tries IPv6 (which must fail for this relayhost), the message > > is deferred. Do subsequent redelivery

Re: Name service error for name=* type=AAAA, when it should be IPv4

2017-03-22 Thread Bastian Blank
Moin On Wed, Mar 22, 2017 at 01:04:36PM -0400, Marvin Renich wrote: > Mar 21 14:42:45 basil postfix/smtp[12587]: 3AF35240229: > to=, relay=none, delay=0.47, > delays=0.25/0.22/0/0, dsn=4.4.3, status=deferred (Host or domain name not > found. Name service error

Re: Name service error for name=* type=AAAA, when it should be IPv4

2017-03-22 Thread Noel Jones
On 3/22/2017 1:08 PM, Marvin Renich wrote: > Thanks, Wietse and Noel. Once the IPv4 delivery fails for some reason, > and Postfix tries IPv6 (which must fail for this relayhost), the message > is deferred. Do subsequent redelivery attempts only try IPv6? This is > what it looked like was

Re: Name service error for name=* type=AAAA, when it should be IPv4

2017-03-22 Thread Marvin Renich
* Wietse Venema [170322 13:14]: > Marvin Renich: > > First, why would the DNS query correctly give the ipv4 address on Mar > > 10, but then fail saying it could not find an ipv6 entry on Mar 21? I > > can find no configuration change or program version change that would > >

Re: Name service error for name=* type=AAAA, when it should be IPv4

2017-03-22 Thread Noel Jones
On 3/22/2017 12:13 PM, Wietse Venema wrote: > Marvin Renich: >> First, why would the DNS query correctly give the ipv4 address on Mar >> 10, but then fail saying it could not find an ipv6 entry on Mar 21? I >> can find no configuration change or program version change that would >> explain this.

Re: Name service error for name=* type=AAAA, when it should be IPv4

2017-03-22 Thread Wietse Venema
Marvin Renich: > First, why would the DNS query correctly give the ipv4 address on Mar > 10, but then fail saying it could not find an ipv6 entry on Mar 21? I > can find no configuration change or program version change that would > explain this. Previously, the A lookup succeeded. Now, the the

Name service error for name=* type=AAAA, when it should be IPv4

2017-03-22 Thread Marvin Renich
I'm having a new problem with ipv6. I'm running Debian (mostly testing release) on my laptop, with Postfix running simply to allow mutt to send when I don't have connectivity. The relevant postconf entries (full postconf -n below): inet_protocols = all (default; not specified in main.cf)