CD
Cloudflare Developers•4mo ago
joennlae

DNS not propagating for @root, *, www but for other subdomain it does. It works for 4/5 domains :-)

Hello everyone 🙂 First of all, it is a fantastic product. I do have some issues with my DNS. I host five domains on Cloudflare, and the service works flawlessly for 4/5 of them. I want to point my domains to an IP without Cloudflare proxying (I do all the SSL termination, etc., on the edge of my k8s cluster). My current DNS settings are attached as an image. I did the following: 1) I check with nslookup if the nameservers are correct 2) reapplied the DNS settings (delete and add again) 3) waited for 24h 4) checked via nslookup from multiple hosts (no local DNS cache confusion) --> It somehow still points inside the Cloudflare CDN network 5) Adding the subdomain test.haidy.health works with any issue. nslookup for (@root, *, www) looks like this: (shortned due to char limit) 
nslookup -debug haidy.health 8.8.8.8
...
    QUESTIONS:
        haidy.health, type = A, class = IN
    ANSWERS:
    ->  haidy.health
        internet address = 172.67.196.231
        ttl = 300
    ->  haidy.health
        internet address = 104.21.52.76
        ttl = 300
...
nslookup -debug haidy.health 8.8.8.8
...
    QUESTIONS:
        haidy.health, type = A, class = IN
    ANSWERS:
    ->  haidy.health
        internet address = 172.67.196.231
        ttl = 300
    ->  haidy.health
        internet address = 104.21.52.76
        ttl = 300
...
What I expect (and it works for the subdomain test.haidy.health: 
nslookup -debug test.haidy.health 8.8.8.8
Server:         8.8.8.8
Address:        8.8.8.8#53

------------
    QUESTIONS:
        test.haidy.health, type = A, class = IN
    ANSWERS:
    ->  test.haidy.health
        internet address = 34.65.XXX.XXX
        ttl = 300
    AUTHORITY RECORDS:
    ADDITIONAL RECORDS:
...
nslookup -debug test.haidy.health 8.8.8.8
Server:         8.8.8.8
Address:        8.8.8.8#53

------------
    QUESTIONS:
        test.haidy.health, type = A, class = IN
    ANSWERS:
    ->  test.haidy.health
        internet address = 34.65.XXX.XXX
        ttl = 300
    AUTHORITY RECORDS:
    ADDITIONAL RECORDS:
...
If you have any idea how I can solve this, please let me know 🙂 Have a good one all 🙂 and cheers
No description
2 Replies
Chaika
Chaika•4mo ago
do you have any other records on that domain? Even just another proxied record AAAA for the same hostname would cause it to all to be proxied btw there's not really any point in censoring dns only domains, the whole thing of dns only is that it's not proxying/protecting your origin's IP and anyone can look it up
dig test.haidy.health +short 34.65.235.253
joennlae
joennlaeOP•4mo ago
Thanks for the answer. My first thought after posting was that the censoring is useless 🙂 But your feedback was correct. Funnily, I have for all other domains proxied AAAA records, and it is only an issue for my .health domain 🙂

Did you find this page helpful?