I've entered the TXT record presented for domain verification, but the verify process never passes. NSLOOKUP and outside tools return the correct DNS information, but the Atlassian domain verification processes doesn't. Any insight would be appreciated.
Can you perform "dig -t 'TXT' <domain> on your terminal and see if the txt record is there?
A working one will have something like this:
dig -t 'TXT' livelyhood.my
; <<>> DiG 9.10.3-P4-Ubuntu <<>> -t TXT livelyhood.my
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34877
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;livelyhood.my. IN TXT
;; ANSWER SECTION:
livelyhood.my. 14399 IN TXT "atlassian-domain-verification=KRN5qAUesvRwN7SWoAirlISC3d+31EJ2TKvNX9Ou6cB9yMsNXzKgDkd3ogtMAmUg"
livelyhood.my. 14399 IN TXT "v=spf1 include:_spf.atlassian.net ~all"
;; Query time: 100 msec
;; SERVER: 10.60.1.180#53(10.60.1.180)
;; WHEN: Thu Aug 16 16:23:35 DST 2018
;; MSG SIZE rcvd: 200
As you can see from above, the Atlassian TXT record is in the server. Can you confirm that the TXT record is there? If it's there, try to increase the TTL and try again.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.