Richard G
Verified User
@jigster @Stije I have found the culprit and cause of the issue. My collegue. He normally adds and removes his own domains, I don't take care of that.
AAARGGHHH... so oke, When testing on the main server, suddenly things went fine. Also DKIM checking was fine.
Then I remembered an old thread with a command to test:
So I started to issue this command on every server.
Main 1 -> no result
Main 2 -> no result
Other -> result ??????
Main 1 and 2 are connecte do each other via multiserver, the others via Directslave.
What is this? I configured all servers the same. Then I checked the extended named logs I create on all servers. There we go... resolution query on 127.0.0.1.
Searched for domain.nl and yes.... my collegue forgot to remove the domain.nl from Main 2. So it also exists in DNS on Main 1 where my company is too and so it got a DKIM issue as all servers resolve 127.0.0.1 for nameservers first.
Pfffff.
Solved...
@Imtek Maybe you can issue that command to on a couple of servers, see if you find a reason for your issue.
AAARGGHHH... so oke, When testing on the main server, suddenly things went fine. Also DKIM checking was fine.
Then I remembered an old thread with a command to test:
dig +notcp +short TXT x._domainkey.server.domain.nlSo I started to issue this command on every server.
Main 1 -> no result
Main 2 -> no result
Other -> result ??????
Main 1 and 2 are connecte do each other via multiserver, the others via Directslave.
What is this? I configured all servers the same. Then I checked the extended named logs I create on all servers. There we go... resolution query on 127.0.0.1.
Searched for domain.nl and yes.... my collegue forgot to remove the domain.nl from Main 2. So it also exists in DNS on Main 1 where my company is too and so it got a DKIM issue as all servers resolve 127.0.0.1 for nameservers first.
Pfffff.
Solved...
@Imtek Maybe you can issue that command to on a couple of servers, see if you find a reason for your issue.
