General ungleich knowledge base » History » Version 2
Jin-Guk Kwon, 05/21/2019 04:38 PM
| 1 | 1 | Nico Schottelius | h1. General ungleich knowledge base |
|---|---|---|---|
| 2 | |||
| 3 | h2. Introduction |
||
| 4 | |||
| 5 | This knowledge base documents topics/problems that we found helpful to not repeat again. |
||
| 6 | |||
| 7 | |||
| 8 | h2. Postfix name resolving issues |
||
| 9 | |||
| 10 | Some of our virtualised servers had the problem that postfix was unable to resolv domains, even though the network configuration (DNS, routing) is correct. The reason for this was an incorrect startup order: postfix was started before the network setup (in our case the opennebula contextualisation) finished. Thus postfix copied the empty /etc/resolv.conf to /var/spool/postfix/etc/resolv.conf and would not update this anymore. |
||
| 11 | |||
| 12 | Typical log lines that we have seen are: |
||
| 13 | |||
| 14 | <pre> |
||
| 15 | Jul 29 21:58:41 mx postfix/error[6542]: 1A8BE211BB: to=<XXXXXXX@gmail.com>, orig_to=<XXXXXXXX@ungleich.ch>, relay=none, delay=1080070, delays=1080069/0.27/0/0.02, dsn=4.4.3, status=deferred (delivery temporarily suspended: Host or domain name not found. Name service error for name=gmail.com type=MX: Host not found, try again) |
||
| 16 | </pre> |
||
| 17 | |||
| 18 | The correct solution is obviously to ensure that postfix is started only after the network is fully up. |
||
| 19 | 2 | Jin-Guk Kwon | |
| 20 | and we need to check vmcontext if postfix run before running vmcontext |