X
Added txt record to domain for a website verify and its not showing up
Checked txt records i added
Go to mxtoolbox and do a txt lookup on the domain and the record doesn’t show up…
Can you please post a screenshot of the TXT record you entered?
This is probably a sure thing, but you’ve added it to the lampshell.net zone that shows Name Servers deborah and paul at the bottom of your DNS Records screen, correct?
Thanks for the screenshot.
I don’t think MX Toolbox will return all TXT records for a domain by default – just the email-related ones.
I can’t see the full hostname of your TXT record, but if you enter it into DNSChecker, like this (replace “SOMETHING” with the rest of that hostname), it should return the content you entered:
Ohh it will, ive used mxtoolbox for about 15yrs because its reliable, its in the dropdown menu. The result is the same with the one you posted though.
It doesn’t return all TXT records for a domain when the root is queried. That’s not how the tool works. You need to replace the ‘something’ with the actual full and correct value from GitHub and query for the FQDN.
Perhaps a FQDN like:
dig _github-pages-challenge-lampshell.lampshell.net TXT +short
"8b55c45c30a76d224563eb1f182bf6"
It doesnt seem its actually putting any of my records in. I just turned off proxy and now mxtoolbox pulls up nothing…
Still resolves that DNS record just fine for me. Make sure you’ve spelled your domain name correctly.
Your root domain doesn’t resolve because you don’t have a record for it.
DNS is a hierarchical tree structure. If you want to query for a record you need to query for the correct node and type.
Actually that is how the tool works there sport, heres one of google.com and the rest is what im seeing…
A records, and AAAA, but no txt
Dude, you’re welcome to double down. Google’s A record looks since OP had a failed upload.
Unfortunately at some point OP deleted his root record in the original DNS screenshot. As a result there’s no root record and the authoritative nameservers correctly reflect this reality. His since deleted screenshots of Mx toolbox returning no valid record for that domain accurately reflect that. Dig also confirms that to be the case.
dig lampshell.net A
; <<>> DiG 9.10.6 <<>> lampshell.net A
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26010
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;lampshell.net. IN A
;; AUTHORITY SECTION:
lampshell.net. 1800 IN SOA deborah.ns.cloudflare.com. dns.cloudflare.com. 2368696887 10000 2400 604800 1800
The TXT record, when queried as needed appears and whether it isvalid or not is a question for the record holder as they are the one who is required to know the correct record name and value.
the txt… not the a…
So txt:google.com
Not a:google.com
And same for mine that doesnt show txt:lampshell.net
Anyways, it automagically verified without my consent finally although i never saw it… was trying things with records and hitting verify button on other side and just kept giving error, then i refreshed page and said verified so wtfe…
Because you don’t have any txt records for lampsheel.net. You have a TXT record for _github-pages-challenge-lampshell.lampshell.net and a query for that resolves as expected.
Google query for their TXT records which all have a name value of google.com (or @ if you prefer).
A query for the record with the label _github-pages-challenge-lampshell when executed against the hierarchical structure that underlies DNS provides the expected value. A query for the root domain for TXT records does not return all TXT records for a domain on any label.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
