Parked domain SPF and DKIM not working
I've parked a domain on an account, set up an email account for that parked domain. The main account has SPF and DKIM enabled and it looks like the proper DNS entries are there. But when I send mail from that account, it acts like SPF and DKIM are disabled.
Example:
SERVER 1
Main IP 1.1.1.1
Account set up example.com
The DNS for example.com has records
*.2 - CNAME - 2.example.com.
2 - A - 2.2.2.2
SERVER 2
Main IP - 2.2.2.2
Main account - example2.com
Parked domain - example2.com.2.example.com
Email account - sender@example2.com.2.example.com
DNS for example2.com.2.example.com has records
default._domainkey - TXT - "v=DKIM1....
example2.com.2.example.com. - TXT "v=spf1....
The website for example2.com.2.example.com pulls up fine. Adding the records to the DNS on server 1 makes it work. Is this a limitation of WHM ignoring the *.2 CNAME for SPF requests? Or is SPF required to always look in the penultimate domain's DNS for any records for subdomains?
-
DNS for example2.com.2.example.com has records default._domainkey - TXT - "v=DKIM1.... example2.com.2.example.com. - TXT "v=spf1....
Hello, Could you verify if those records are added to the DNS host for example.com? Thank you.0 -
Hello, Could you verify if those records are added to the DNS host for example.com? Thank you.
It does work if they are added to the DNS zone for example.com on server 1.0 -
It does work if they are added to the DNS zone for example.com on server 1.
This is required, as the remote mail servers will check for the records on the server defined as the DNS host for the parent domain name. Thank you.0 -
I got it to work.... I added NS records in the zone for example.com on server 1 to point to server 2... that seems to fix it. 0 -
I'm happy to see the issue is now resolved. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
5 comments