-1

My server is modalduality.org and I have a DKIM record at 201703._domainkey.modalduality.org.

When I run

dig 201703._domainkey.modalduality.org TXT

I get back the correct record in the ANSWER SECTION sometimes, but other times I only get an NXDOMAIN error, the AUTHORITY SECTION, no ANSWER SECTION, and I don't get the DKIM record as a result. If I run it ten times in a row maybe half will show the correct result. What could be causing this behavior? I'm using Namecheap to set my DNS, cname for the dkim key points to a Cloudns subdomain.

1 Answers1

0

Probably you get results from different NS servers or local cache. First, try to specify NS server you want to query, as far 'dig' it will be:

dig mydomain.org @ns1.mydomain.org

and check if it returns correct value each time you query it. I suppose it solves your problem.

adoado0
  • 101
  • 8
  • Yes, I think the issue was I was querying different paths and some of them were old. Seems to work fine now, thanks. – modalduality Feb 23 '17 at 11:50