Re: systemd-resolved ipv6 resolving issue

2016-12-03 Thread Henning Follmann
On Fri, Dec 02, 2016 at 09:33:48AM -0500, Henning Follmann wrote: > Hello, > > I do have a weird issue. First the story. > > I switch a new debian install (jessie) from the /etc/network/interfaces > setup over to systemd-networkd. In addition I also enabled systemd-resolvd. > The address

Re: systemd-resolved ipv6 resolving issue

2016-12-02 Thread Henrique de Moraes Holschuh
On Fri, 02 Dec 2016, Henning Follmann wrote: > correctly now. However the two test mails were stuck in the queue. Even a > forceful flush did not convince postfix to lookup the smarthost again. You can use "postsuper -r " to fix this kind of issue in the future. -- Henrique Holschuh

Re: systemd-resolved ipv6 resolving issue

2016-12-02 Thread Henning Follmann
On Fri, Dec 02, 2016 at 04:53:38PM +0100, Markus Schönhaber wrote: > Henning Follmann, Fr 02 Dez 2016 15:33:48 CET: > > > Why does postfix even try to get the record. Documentation states > > actually that if not provided t defaults to: > > inet_protocols = ipv4 > > No, the documentation

Re: systemd-resolved ipv6 resolving issue

2016-12-02 Thread Liam O'Toole
On 2016-12-02, Henning Follmann wrote: > Hello, > > I do have a weird issue. First the story. > > I switch a new debian install (jessie) from the /etc/network/interfaces > setup over to systemd-networkd. In addition I also enabled systemd-resolvd. > The address

Re: systemd-resolved ipv6 resolving issue

2016-12-02 Thread Markus Schönhaber
Henning Follmann, Fr 02 Dez 2016 15:33:48 CET: > Why does postfix even try to get the record. Documentation states > actually that if not provided t defaults to: > inet_protocols = ipv4 No, the documentation states | inet_protocols (default: all)