Issue with Extra Nameserver (ns3.byet.org) – How to Fix?

What is the name of the domain?

kiranpant.com.np

What is the issue you’re encountering

Extra Nameserver (ns3.byet.org)

What feature, service or problem is this related to?

Nameservers

What are the steps to reproduce the issue?

I noticed that I have an extra nameserver (ns3 byet org) in my settings, but at registration, I only provided two. I can only add two nameservers, and the third one seems to be an old entry. I’m unsure how to resolve this issue.

I’m trying to replace my nameservers with Cloudflare’s:

However, ns3 byet org is still there. Any advice would be appreciated!

Contact your domain registrar and tell them that the .np registry is showing this extra nameserver although you’ve only set the 2 Cloudflare nameservers according to WHOIS. They will need to fix it.

kiranpant.com.np.	86400	IN	NS	ns3.byet.org.
kiranpant.com.np.	86400	IN	NS	amit.ns.cloudflare.com.
kiranpant.com.np.	86400	IN	NS	brenda.ns.cloudflare.com.
;; Received 128 bytes from 2001:67c:e0::102#53(np.cctld.authdns.ripe.net) in 4 ms

I’ve seen this sort of problem several times with .np domains.

2 Likes

Thanks I will I tried with 8.8.8.8 and 1.1.1.1 and they looked correct but the Authority still seems to show 3 NS.

Those are returning NS records from the DNS. That will show correctly (mostly), it is the authoritative nameservers that are wrong at the registry, as here…
https://cf.sjr.dev/tools/check?d9309c4b783d43ecadb4229f28f28ac3#dns

That can only be fixed by the registry via the registrar.

3 Likes

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