Created a NS records to a sub-domain but it's not publicly available

What is the name of the domain?

kmteam.tech

What is the issue you’re encountering

I’ve created a NS records to a sub-domain but it’s not publicly available

What steps have you taken to resolve the issue?

waited for a week

What feature, service or problem is this related to?

Nameservers

Screenshot of the error

You pointed proto to ns<1-4>.byet.org. Cloudflare’s serving that delegation fine but ns<1-4>.byet.org are refusing queries for your domain.

; EDNS: version: 0, flags:; udp: 1232
; EDE: 22 (No Reachable Authority): (at delegation proto.kmteam.tech.)
; EDE: 23 (Network Error): (198.251.86.154:53 rcode=REFUSED for proto.kmteam.tech A)

dig proto.kmteam.tech @ns2.byet.org
; <<>> DiG 9.18.24-1-Debian <<>> proto.kmteam.tech @ns2.byet.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 21516
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

This usually means they haven’t been configured to accept queries for that dns zone (proto.kmteam.tech). You’ll have to reach out to the operators of ns1-4.byet.org for more info.

2 Likes

First, please check your NS records are correctly configured in your DNS setting and make sure your NS records are correctly pointing to authorative nameservers for your subdomain. You might be seeing this a small task and thinking that how can I forget such a small task but some time small errors make a lot of problems. This has happened with me and I created a mess at that time. so please check that if that is not the problem you can ask me to get more checks.

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