My domain julesdocx.be is configured in my DigitalOcean DNS panel but your nameservers are returning NXDOMAIN responses, preventing the domain from resolving.
Domain Details:
- Domain:
julesdocx.be - Nameservers set at registrar (GoDaddy): ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
- Nameserver change made: Over 24 hours ago
- Current status: Domain appears properly configured in DigitalOcean DNS panel
Technical Evidence:
$ dig @ns1.digitalocean.com julesdocx.be
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN
;; OPT=15: "Result from negative cache for entire name"
What I’ve verified:
- ✅ Domain exists in my DigitalOcean DNS panel with correct A record
- ✅ Nameservers properly delegated at registrar for 24+ hours
- ✅ DigitalOcean’s DNS lookup tool also doesn’t recognize the domain
- ❌ All DigitalOcean nameservers return NXDOMAIN
Suspected Issue: This appears to be a negative DNS caching issue on DigitalOcean’s side where your nameservers are stuck serving cached NXDOMAIN responses even though the domain is properly configured.
Request: Please investigate and clear any negative cache entries for julesdocx.be in your DNS infrastructure.
Account: jules.docx@gmail.com
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hey there,
From what I can see when running a quick whois , your domain julesdocx.be is still pointing to the default NSSET.BE nameservers:
whois julesdocx.be | grep nserver
nserver: A.NSSET.BE 194.0.6.1 2001:678:9:0:0:0:0:1
nserver: B.NSSET.BE 194.0.37.1 2001:678:64:0:0:0:0:1
nserver: C.NSSET.BE 194.0.43.1 2001:678:68:0:0:0:0:1
nserver: D.NSSET.BE 194.0.44.1 2001:678:6c:0:0:0:0:1
nserver: Y.NSSET.BE 120.29.253.8 2001:dcd:7:0:0:0:0:8
nserver: Z.NSSET.BE 194.0.25.36 2001:678:20:0:0:0:0:36
So even though the domain is fully configured in your DigitalOcean DNS panel, DigitalOcean’s nameservers aren’t actually authoritative for the domain yet, that’s why you’re getting the NXDOMAIN response.
If I remember correctly form the days when I used to work at a web hosting company, for .be domains the DNS Belgium registry requires that the new nameservers already serve valid DNS records for the domain before they accept the change. If not, the update might silently fail or just revert to the old nameservers. Things might have changed since though.
As you’ve already done the first step by adding the domain and its records in your DigitalOcean DNS panel, the next step is to go back to your registrar (GoDaddy) and set the nameservers to:
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com
After that, give it a bit of time and verify with:
whois julesdocx.be | grep nserver
dig julesdocx.be +trace
Once the registry sees valid zone data being served by the DO nameservers, the delegation should go through properly and the NXDOMAIN issue will clear up.
If this still does not work it is probably worth reaching out to GoDaddy’s support and asking them to check the status of the domain.
Let me know how it goes!
- Bobby
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.