Propagation doesnot work for my domain, no change from my side

Website, Application, Performance DNS & Network
1

Hello Guys!

I dont do any change in my Cloudflare, but slowly my DNS stop of begin propagated.

There some partial outage in CF status page, but i dont know this is the problem.

In NS 172.64.35.213(karsyn.ns.cloudflare.com), i can resolve the DNS, but my Cloudflare records is not resolved in any part of the world, as i can see in https://www.whatsmydns.net .

The DNS propagation is slow, i know, but old entry stop work is not a normal case. This is the first time, the propagation is taking a long time and i not made any change.

There is any kind of clue to understand what is happening?

Thanks in advanced!

2

For informations about the domain:

https://www.whatsmydns.net/#CNAME/weni.ai

I cannot see the NS entry in .ai, this can be something?

3

I cannot view the NS entry in ai.:

dig weni.ai @pch.whois.ai. NS

; <<>> DiG 9.18.7 <<>> weni.ai @pch.whois.ai. NS
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54516
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 943a49d1b754cd3d9beb76556392848fa5860adefecdf87f (good)
;; QUESTION SECTION:
;weni.ai.                       IN      NS

;; AUTHORITY SECTION:
ai.                     86400   IN      SOA     pch.whois.ai. vince.offshore.ai. 2022120818 21600 3600 86400 86400

;; Query time: 166 msec
;; SERVER: 2001:500:14:6123:ad::1#53(pch.whois.ai.) (UDP)
;; WHEN: Thu Dec 08 21:42:55 -03 2022
;; MSG SIZE  rcvd: 129
4

Someone has changed your nameserver at your registrar to incorrect values.

Name Server: ishaan.ns.cloudflare.com
Name Server: karsyn.ns.cloudflare.com
Name Server: dahlia.ns.cloudflare.com
Name Server: lakas.ns.cloudflare.com

You should have a single pair assigned from your active Cloudflare account. Correct this and remove access to your registrar from whoever made the unauthorized change.

2 Likes
5

Its me who made this change, trying to replicate a DNS config who was working on another domain. But, before that, the nameserver is working, i made this to try to fix him. And, as i know and see, if there a extra nameserver in config, this not will broke the propagation.

My problem is resolved, my team contact the parent domain admin, how is a very good and helpful person, and he say something about godaddy block my domain and it was preventing the propagation. I dont know what he means by “block domain” or if is godaddy or CF the guy how is blocking, but now is working again.

Thanks for the attention.

6

It does not appear to be fixed. @cscharff’s advice still applies.

7

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.