ns.cloudflare.com
ns.cloudflare.com has only A records but none for AAAA. This is problematic as i am using this nameserver frontend for checking ACME TXT records.
Nameservers
The name servers are normally in the format “{NAME}.ns.cloudflare.com” .
So I’m wondering, -
What exactly gave you the idea, that you should be able to use “ns.cloudflare.com”, like you’re trying to do, or for anything at all?
Can you explain how this works, and what the purpose of it is / why you’re doing this?
I’m using GitHub - socram8888/dehydrated-hook-cloudflare: Pure bash dehydrated dns-01 hook for CloudFlare to create the TXT records with dehydrated.
After looking into the code i assumed ns.cloudflare.com is a resolver/nameserver which has the internal nameservers as stub zone hints. This created some problems on my machines without IPv4 adresses.
The check inside the code is to verifiy that the record is actually delivered by the cloudflare nameservers. At this point you don’t want to rely on resolvers because also they do caching.
Nevertheless is the question why there is a domain where only a A record exists when the whole cloudflare infrastructure is dual-stack.
That tool is using a resolver it shouldn’t. Replace it with either a lookup to determine the correct authoritative nameservers for a zone or query a public resolver.
As to why it doesn’t have IPv6 addresses… 
.. no one in the community can answer that, but it’s not intended for purpose.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.