Domain not reachable after switching NS to CF

[oliver15]

Hi, community!
I struggle with setting up my website wit CF, I guess.
What I’ve done:
I deleted my nameservers in my DNS and replaced them with the given IMANI and NICO, like told me to do.
Since then, my website isnt accessible anymore.
CF Dashboard sais: All fine
CF troubleshooter: Error 530 w/o any other 1xxx error
My Browser sais: DNS_PROBE_FINISHED_NXDOMAIN
NMAP sais:
"Nmap scan report for xxx (172.67.191.14)
Host is up (0.022s latency).
Other addresses for xxx (not scanned): 2606:4700:3034::6815:5465 2606:4700:3033::ac43:bf0e 104.21.84.101
Nmap done: 1 IP address (1 host up) scanned in 6.80 seconds"
The IPs doesn’t match ServerIP of domain.
WHOIS sais:
"whois xxx

• Domain Name: XXX*
• Name Server: IMANI.NS.Cloudflare.XXX*
• Name Server: NICO.NS.Cloudflare.XXX*
• DNSSEC: unsigned"*

Whats going on and how can I fix this?
Thanks!

[Albertus]

What whois shows isn’t always what’s happening at the DNS level.

Your domain is most likely still pointing to your old DNSs, or the DNS resolver you’re using still has it cached.

I would suggest to perform a dig +trace query.

[fritex]

Greetings,

Thank you for asking.

@oliver15

DNS_PROBE_FINISHED_NXDOMAIN

May I ask what steps have you tried for troubleshooting from the article below?

Community Tip - Fixing the DNS PROBE FINISHED NXDOMAIN error

Error Try the suggestions in this Community Tip to help you fix DNS_PROBE_FINISHED_NXDOMAIN. Background NXDOMAIN stands for non-existent domain. When a domain cannot be resolved it is an issue with the DNS servers or the domain name is newly registered or not yet registered at all. NXDOMAIN can also take place due to network or DNS server problems. A response other than a valid IP address (e.g., timeout, SERVFAIL, NXDOMAIN or NOERROR) most likely points to the origin as the source of your iss…

Without knowing your domain name, I could only guess:

1. Missing A record pointed to IP
2. DNSSEC was enabled before changing domain nameservers
3. Cloudflare nameservers being added as “private nameservers” instead of the domain nameserver change at registrar
4. CNAME issue
5. Nameserver spelling (or/not using copy-paste)
6. DNS cache issue at local ISP

@oliver15

Domain Name: XXX*

Kindly, can you share your domain name here with us so we could double-check and provide further assistance?

[oliver15]

Guys,…

thanks for your assistance:

Sometimes you have to deal with n00bs like me and I feel very sorry for you.
I just “fixed” it by myself. All is working now.
No, you dont want to know, what the reason for the “failure” was.

Regards,