Skip to main content

SPF/DMARC/DKIM failed to complete validation

Answered
maestroc

I have a domain (precisioninvestigativegroup.com) that according to the Email Deliverability thing in cpanel says that DKIM, SPF, and DMARC are failing because:

The system failed to complete validation of “precisioninvestigativegroup.com”’s “DKIM” because of an error: (XID pzdgqg) DNS query (default._domainkey.precisioninvestigativegroup.com/TXT) timeout!

After reading through some of the posts in this forum I ran the command below via WHM's terminal:

dig txt default._domainkey.precisioninvestigativegroup.com 

The first time I ran it it came back with:

; <<>> DiG 9.16.23-RH <<>> txt default._domainkey.precisioninvestigativegroup.com
;; global options: +cmd
;; connection timed out; no servers could be reached

Then a minute later I ran it again and received a response:

; <<>> DiG 9.16.23-RH <<>> txt default._domainkey.precisioninvestigativegroup.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61780
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;default._domainkey.precisioninvestigativegroup.com. IN TXT

;; ANSWER SECTION:
default._domainkey.precisioninvestigativegroup.com. 14400 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvA6XvkQtP2d/hwPWnN356CBzXUlI6cbDWekXg7adEJhrOKIvHywMJkJ79MY95/KUC5nG9+ZD5ZXhsiBtw/5ubiogz/v2CoGw4GF4ZtrmxvwgrL7Smx8lc2bSrCR2xxTmF4z2whiyfiAQyDvQNGBVw7IuxcmAjXn3SD/noCECQCWv8sLxDEUQN7cNUZJCPD1II" "w+jBYnWLUTJbSbjX53QGf6CbaBI/ox2k5Wl4LrHd5MB2shUriYe//jpMXkoQpa3NvmwVSJldaWxH7Fwp5Q2gdgPJx9T4Nb2yyvcVcjHsBHVKRf8l9DcSJEtKUNNqjcZWYMH90i4XYnm4vn/LkNcTQIDAQAB;"

;; Query time: 68 msec
;; SERVER: 4.2.2.2#53(4.2.2.2)
;; WHEN: Sun Mar 16 15:10:01 CDT 2025
;; MSG SIZE  rcvd: 504

However, email is not being received in the account and Email Deliverability continues to say the same timeout error messages.

I have already tried restarting exim as I had seen in another post.

Comments

2 comments

Date Votes
  • maestroc

    Never mind.  I discovered the problem right after posting this (as usual)...  It turned out to be a nameserver issue.  DNS was pointing to our old NS instead of the new one.

    0
  • cPRex Jurassic Moderator

    I'm glad things are working well for you now!

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post