Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,450
Community Members
 
Community Events
176
Community Groups

DNS Domain Verification

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.

1 answer

0 votes
Hazwan Atlassian Team Aug 16, 2018

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.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events