3 ms·
> Some have A records pointing to the root servers. I’m not sure why this is - I think it might be because no DNS has been configured in the TLD zone for these
by matttpt 4y ago
> Some have A records pointing to the root servers. I’m not sure why this is - I think it might be because no DNS has been configured in the TLD zone for these TLDs.
I was also curious about this. It turns out that it's because dig interprets some TLDs as DNS record types (MD, MG, MR, MX) or DNS classes (IN and CH) of the same name! Not sure why, but when given only a type or class (without a domain name), dig actually queries for a list of the root servers, which explains the strange results. Looks like using the -q option to specify the domain name works around this.
- jamespwilliams 4y agoOh interesting, thanks! I fixed the script and ran the TLD list through again, in case this meant I missed some, but none of the affected TLDs have A records. I'll update my post to mention your comment.
- N6VjeuHbGSwMN9e 4y agoOr you could just make it a FQDN: `dig @8.8.8.8 MX.`
- chedabob 4y agoThere was a post recently about some of these TLDs: https://news.ycombinator.com/item?id=32094645 https://news.ycombinator.com/item?id=32094645