Dig not showing cloudflare as part of the DNS chain

Website, Application, Performance DNS & Network
1

What is the name of the domain?

kao.cloudns.be

What is the issue you’re encountering

nameserver doesn’t seem to resolve my domain name

What feature, service or problem is this related to?

I don’t know

What are the steps to reproduce the issue?

dig +trace kao.cloudns.be

the chain ended with ns51.cloudns.net

2

As a new user I can only create ticket with 4 links. so the full trace is not available to attach

dig +trace kao.cloudns.be

; <<>> DiG 9.10.6 <<>> +trace kao.cloudns.be
;; global options: +cmd
.			471063	IN	NS	a.root-servers.net.
.			471063	IN	NS	e.root-servers.net.
.			471063	IN	NS	k.root-servers.net.
.			471063	IN	NS	j.root-servers.net.
.			471063	IN	NS	h.root-servers.net.
.			471063	IN	NS	d.root-servers.net.
.			471063	IN	NS	m.root-servers.net.
.			471063	IN	NS	l.root-servers.net.
.			471063	IN	NS	f.root-servers.net.
.			471063	IN	NS	g.root-servers.net.
.			471063	IN	NS	c.root-servers.net.
.			471063	IN	NS	b.root-servers.net.
.			471063	IN	NS	i.root-servers.net.
.			471063	IN	RRSIG	NS 8 0 518400 20240914050000 20240901040000 20038 . iO0lQElEf6JTgXIzple7x7uSeMOovdy3VysmM6qhcnmZd0HdlZmU+Hj/ YkRyj7zi2BdeDQGSHmnVkwAz4lyqBsSKOxXJUGEvMYi4qIBx/btOfvIi sksgZT+e5LvJ75vGR9RLyO2i8pAhkcZKDXy0SpwkjVidXht8fIE46Q/9 RFQ8YPb78H4+i6Qp2XzzpbJg4LWvKocy3qAmqeEt0o6DTwHFPZoz9s3R 2pdJcIiLYvi1UsfFjJOA5Ay/gLJ0jGqREL+ft7bLIU+9147Itvj3Glfx /10nOgEwr+FB14wJfj+rjC/2Z9A7pgV1m01GzYOXc9xe65P7AuvpkgbF 3KuKyg==
;; Received 1097 bytes from 192.168.1.1#53(192.168.1.1) in 66 ms

be.			172800	IN	NS	y.nsset.be.
be.			172800	IN	NS	a.nsset.be.
be.			172800	IN	NS	b.nsset.be.
be.			172800	IN	NS	c.nsset.be.
be.			172800	IN	NS	d.nsset.be.
be.			172800	IN	NS	z.nsset.be.
be.			86400	IN	DS	12664 8 2 75141E9B1188A95A7A855BF47E278A742A5E3F2DDEED8E995D749D48 F2F0E72D
be.			86400	IN	DS	52756 8 2 5485AC33DD7C7ED237EA2A4BD269731C816960FE181042024484B5CE CA6ECC9F
be.			86400	IN	RRSIG	DS 8 1 86400 20240914170000 20240901160000 20038 . Tqy2GdxyRWoWIg3zZzWlryRG7clGRVFIqJPsAIYcN15mN36NoA+nA2fD YHduUpD5saBOyyHWDieebpb9f5VVMyZ6Oi3Ukxlx2GSUzKD1GkxYpLru M8x3DE4aSz7QF2QkvMeHpGL+zkU65wPioiFzlND+zuN1I/OJUdQxxjE2 8m9ah1M3yrAa1eQIn8fACiQhvP4QSqdouI+44vz8KeLMCrzRnxP0Lyev FGV6WByh2owV+6eEzjMZVTBIAI96yYE6k+jfjHUlGQ0KUt6qalgShYXO H0lfRt0gNgfjTz64Gev2ulrES3Mtw9kFBS/zlfWKfexMsHlOBgvFo1ys E3hsww==
;; Received 796 bytes from 192.112.36.4#53(g.root-servers.net) in 94 ms

cloudns.be.		86400	IN	NS	ns53.cloudns.net.
cloudns.be.		86400	IN	NS	ns51.cloudns.net.
cloudns.be.		86400	IN	NS	ns52.cloudns.net.
cloudns.be.		86400	IN	NS	ns54.cloudns.net.
PDRPQGS0T19R8QUL7C2H4BHNB7AGH1B8.be. 600 IN NSEC3 1 1 0 - PDRRMAHC5LLBO4DHP1J3TFP2JERSM6G0  NS SOA RRSIG DNSKEY NSEC3PARAM
PDRPQGS0T19R8QUL7C2H4BHNB7AGH1B8.be. 600 IN RRSIG NSEC3 8 2 600 20240922150616 20240830215512 23343 be. d+/Wu1BC6WsH141h6Y3sm9O+XdDSiCxiYR6W7gu3uiDWrO5ecQSUiSz5 Y0NIDy6HgtIUBypmaGYAyRAOlI8f9hEElTQkJ2wC/EbMGyJtYjfhPzoT PK49Bff+4T5uzLt4oVKHimRpPQJeZ5DiXpkvDUP4CXOlW0ccq6F3S9/7 3Oc=
BGSRI44V74FRFMA0L6MOM0MG6JAD6KG6.be. 600 IN NSEC3 1 1 0 - BGSVFU95746TKPLHPAC403V08F2J1DN0  NS DS RRSIG
BGSRI44V74FRFMA0L6MOM0MG6JAD6KG6.be. 600 IN RRSIG NSEC3 8 2 600 20240919212847 20240829205217 23343 be. Y7W4V2qG//azKBlr8I1Z/RYOC/6CpKh+wqcL0vhf1mlXIdPWS8PSMr1S teZpGN52JydnHQTK0l+6esKqv9tB/ijJsTzHu39ZUnJiSXHmnyCaeuRM /5Sq9TSZVWMzD3T4WCOFayKEBKy3D06g8Yeltjr+zByyRYNHtm2Re+FL W8M=
;; Received 615 bytes from 120.29.253.8#53(y.nsset.be) in 27 ms

kao.cloudns.be.		3600	IN	SOA	ns51.cloudns.net. support.cloudns.net. 2024090208 7200 1800 1209600 3600
;; Received 103 bytes from 5.161.229.185#53(ns52.cloudns.net) in 92 ms

I would expect it to end with

or martin.ns.cloudflare.com

I have added these as the NS record in cloudns.net’s record.

3

This is because Cloudns doesn’t delegate properly (I think you need a paid account with them to change the SOA).

Same as others…

2 Likes
4

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