NS - Record not found!

What is the name of the domain?

jokerbet.biz

What is the error number?

Services do not see NS records

What is the error message?

Record not found!

What is the issue you’re encountering

NS- Record not found!

What steps have you taken to resolve the issue?

I made NS in the table, but no service sees them. I did the same thing before and it worked. Can you tell me what the reason might be?

What feature, service or problem is this related to?

DNS records

What are the steps to reproduce the issue?

I made NS in the table, but no service sees them. I did the same thing before and it worked. Can you tell me what the reason might be?

Screenshot of the error

Sorry i have attached wrong screen, Its correct.

The delegation for track is in place and the selzy.com nameservers are responding with NS records for it so seems to be ok.

jokerbet.biz.		3600	IN	NS	emily.ns.cloudflare.com.
jokerbet.biz.		3600	IN	NS	trey.ns.cloudflare.com.
;; Received 131 bytes from 156.154.127.65#53(c.gtld.biz) in 3 ms

track.jokerbet.biz.	3600	IN	NS	uns1.selzy.com.
track.jokerbet.biz.	3600	IN	NS	uns2.selzy.com.
track.jokerbet.biz.	3600	IN	NS	uns3.selzy.com.
;; Received 113 bytes from 2606:4700:58::adf5:3bf2#53(trey.ns.cloudflare.com) in 3 ms

track.jokerbet.biz.	3600	IN	NS	uns2.selzy.com.
track.jokerbet.biz.	3600	IN	NS	uns3.selzy.com.
track.jokerbet.biz.	3600	IN	NS	uns1.selzy.com.
;; Received 113 bytes from 195.13.229.163#53(uns2.selzy.com) in 39 ms
1 Like

Yes, the track subdomain is now visible, but for some reason the send subdomain is not visible.

The delegation is in place, but send is not configured in the selzy.com nameservers…

jokerbet.biz.		3600	IN	NS	emily.ns.cloudflare.com.
jokerbet.biz.		3600	IN	NS	trey.ns.cloudflare.com.
;; Received 130 bytes from 204.74.105.1#53(m.gtld.biz) in 11 ms

send.jokerbet.biz.	3600	IN	NS	uns1.selzy.com.
send.jokerbet.biz.	3600	IN	NS	uns2.selzy.com.
send.jokerbet.biz.	3600	IN	NS	uns3.selzy.com.
;; Received 112 bytes from 2606:4700:58::adf5:3bf2#53(trey.ns.cloudflare.com) in 3 ms

;; Received 46 bytes from 195.13.229.163#53(uns2.selzy.com) in 39 ms


dig +nodnssec send.jokerbet.biz ns @uns1.selzy.com

; <<>> DiG 9.18.28-0ubuntu0.22.04.1-Ubuntu <<>> +nodnssec send.jokerbet.biz ns @uns1.selzy.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 3322
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;send.jokerbet.biz.		IN	NS

;; Query time: 39 msec
;; SERVER: 195.13.229.67#53(uns1.selzy.com) (UDP)
;; WHEN: Mon Aug 05 09:21:22 UTC 2024
;; MSG SIZE  rcvd: 46


dig +nodnssec send.jokerbet.biz a @uns1.selzy.com

; <<>> DiG 9.18.28-0ubuntu0.22.04.1-Ubuntu <<>> +nodnssec send.jokerbet.biz a @uns1.selzy.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 22885
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;send.jokerbet.biz.		IN	A

;; Query time: 39 msec
;; SERVER: 195.13.229.67#53(uns1.selzy.com) (UDP)
;; WHEN: Mon Aug 05 09:22:03 UTC 2024
;; MSG SIZE  rcvd: 46
2 Likes

It’s very strange why I don’t see this in Toolbox

This often confuses people.

You are asking for the NS records the same way as if you asked for any other record (A, AAAA, MX, TXT, etc). You have delegated send to selzy.com nameservers so even requests for NS records will be delegated to them, and as you haven’t set the records there, there’s no answer.

Same as when you ask for the NS records for track, the answer is coming from the selzy.com nameservers, which you have set up.

The NS records you have set at Cloudflare can be seen when you do a trace as I did above and indicate the delegation. Your Cloudflare configuration is correct, you need to add the records for send in the selzy.com nameservers.

2 Likes

Thank you a lot.

1 Like

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