DKIM with internal DNS [message #146955] |
Fri, 01 November 2019 12:16  |
claudia.c
Messages: 1 Registered: November 2019
|
|
|
|
Hi all,
We use 5 domains with Kerio Connect (9.2.5 - p3).
I have managed to set up DKIM records for all domains, except for the primary domain.
We use OS X Server (v5.2) for internal DNS and Kerio is in the same local network.
When I activate DKIM in Kerio for the primary domain, it says: "DKIM public key for [domain.com] is wrong".
I created a DKIM TXT record at our internet hosting service and although this works perfectly with the other domains, this doesn't work with the primary domain.
Can I, or should I even, create the DKIM TXT record in the DNS settings of our OS X Server?
Would Kerio look at the internal DNS and accept the valid DKIM record, while receiving mailservers would look at the TXT record at our internet hosting service to check for the DKIM record?
Does anyone know if this would solve the problem or am I overlooking something?
Thanks!
Claudia
|
|
|
Re: DKIM with internal DNS [message #146958 is a reply to message #146955] |
Fri, 01 November 2019 20:34  |
j.a.duke
Messages: 239 Registered: October 2006
|
|
|
|
Quote:We use 5 domains with Kerio Connect (9.2.5 - p3).
I have managed to set up DKIM records for all domains, except for the primary domain.
We use OS X Server (v5.2) for internal DNS and Kerio is in the same local network.
When I activate DKIM in Kerio for the primary domain, it says: "DKIM public key for [domain.com] is wrong".
I created a DKIM TXT record at our internet hosting service and although this works perfectly with the other domains, this doesn't work with the primary domain.
Can I, or should I even, create the DKIM TXT record in the DNS settings of our OS X Server?
Would Kerio look at the internal DNS and accept the valid DKIM record, while receiving mailservers would look at the TXT record at our internet hosting service to check for the DKIM record?
Does anyone know if this would solve the problem or am I overlooking something?
Claudia,
Which DNS servers are configured on your Connect server (either virtual or physical)? If I read your response correctly, only internal.
If it's looking at the internal DNS, then set it up on OS X Server, but if the Connect server is looking only at external DNS, then you need to figure out why the external record isn't being acknowledged.
I have a similar problem. My Connect server looks at only internal DNS, but I can't get a DKIM record working on any internal DNS that I've tried (macOS server, Synology, BIND running on a Mac via DNS Enabler). I'm currently getting ready to test NSD installed via homebrew, but haven't had the time to create the zone file for testing.
The problem appears to be the record length - it is truncated or not returned correctly when Connect tries to verify the record in DNS. I've followed the various write-ups that discuss how to break the line length up so that it should work. But unfortunately, it doesn't, at least for me.
Cheers,
Jon
|
|
|