Found an interesting issue with a customer this week, when opendkim wouldn't start, even though ldap was running on the same server.
the keytable & signing table both pointed to:
The ldap server for mx1.domain.com was bound to 192.168.1.52 (example IP)
But the IP for mx1.domain.com in DNS was 188.8.131.523 (example IP)
OpenDKIM would fail to start because it could not connect to 184.108.40.2063. However, /etc/hosts had both IPs for the host in it:
So it seems that when doing resolution, /etc/hosts is bypassed with OpenDKIM for the LDAP server.
Log in to post a comment.