Just as an update: Our loadbalancers have troubles with dns responses which contain several hosts. For some domains they corrupt the dns cache on the loadbalancer and therefore deliver such bogus responses. This behaviour even occurs if no dns cache settings are set on the loadbalancer. The manufactor (a10 networks) opened a bug report and will fix the issue in a future software release.
So it never was a postfix problem :-) Am 11.06.2015 um 15:40 schrieb Viktor Dukhovni: > On Thu, Jun 11, 2015 at 12:23:47PM +0000, Viktor Dukhovni wrote: > >> >>> ogrj.ch. 3057 IN MX 10 smtasg01.abxsec.com. >>> ogrj.ch. 3057 IN MX 20 smtazh01.abxsec.com. >>> ogrj.ch. 3057 IN MX 110 smta2.abxsec.com. >>> ogrj.ch. 3057 IN MX 120 smtp1.seabix.com. >>> ogrj.ch. 3057 IN MX 130 smta4.abxsec.com. >>> ogrj.ch. 3057 IN MX 140 smta3.abxsec.com. >>> ogrj.ch. 3057 IN MX 510 mtas.abxsec.com. >>> ogrj.ch. 3057 IN MX 520 mtaz.abxsec.com. >>> >>> Jun 11 11:09:07 smtp2 postfix/smtp[19862]: warning: no MX host for >>> ogrj.ch has a valid address record >> >> There was a problem looking up the addresses of the above hosts, >> perhaps a nameserver was down, or a network connectivity problem >> prevented access. >> >>> Jun 11 11:09:07 smtp2 postfix/smtp[19862]: 2B25317FA69: >>> to=<removed_for_priv...@ogrj.ch>, relay=none, delay=0.18, >>> delays=0.15/0/0.03/0, dsn=5.4.4, status=bounced (Host or domain name >>> not found. Name service error for name=smtp1.seabix.com type=A: Host >>> not found) >> >> Postfix logged the problem for one of the MX hosts. > > However, given that the message then bounced, the problem did not > manifest as a transient problem. For some reason at the time in > question the MX RRset authoritatively did not contain any hosts > that had an IP address and it looks like "smtp1.seabix.com" was > the last host by MX preferene. >
signature.asc
Description: OpenPGP digital signature
