Pending nameserver - configured according to your doc. Is there anaother error?

I configured the server according to the doc, and merkle-fam.de is shown as provided by cloudflare:
what else should I do?
I can’t show the complete dig output, it is not allowed :frowning:
;; ANSWER SECTION:
merkle-fam.de. 10005 IN NS oxygen-ns-aa
merkle-fam-aa 10005 IN NS helium-ns-aa
merkle-fam-aa 10005 IN NS hydrogen-ns-aa
merkle-fam-aa 10005 IN NS joaquin.ns.cloudflare.com.

there is an additional hetzner ns - but it is not configured on hetzner DNS:

which is empty :slight_smile: - in this sense.

What can I do?

You must only include the 2 Cloudflare nameservers at your registrar.
https://cf.sjr.org.uk/tools/check?534c8de153b0471b860699951d21d4df#dns

Those must be removed.

2 Likes

Hi there,

In order for the zone to become active in Cloudflare, your assigned nameservers must be the only ones:

dig NS merkle-fam.de  +trace

; <<>> DiG 9.10.6 <<>> NS merkle-fam.de +trace
;; global options: +cmd
.			513026	IN	NS	a.root-servers.net.
.			513026	IN	NS	b.root-servers.net.
.			513026	IN	NS	c.root-servers.net.
.			513026	IN	NS	d.root-servers.net.
.			513026	IN	NS	e.root-servers.net.
.			513026	IN	NS	f.root-servers.net.
.			513026	IN	NS	g.root-servers.net.
.			513026	IN	NS	h.root-servers.net.
.			513026	IN	NS	i.root-servers.net.
.			513026	IN	NS	j.root-servers.net.
.			513026	IN	NS	k.root-servers.net.
.			513026	IN	NS	l.root-servers.net.
.			513026	IN	NS	m.root-servers.net.
;; Received 239 bytes from 127.0.2.2#53(127.0.2.2) in 66 ms

de.			172800	IN	NS	l.de.net.
de.			172800	IN	NS	f.nic.de.
de.			172800	IN	NS	a.nic.de.
de.			172800	IN	NS	z.nic.de.
de.			172800	IN	NS	s.de.net.
de.			172800	IN	NS	n.de.net.
de.			86400	IN	DS	26755 8 2 F341357809A5954311CCB82ADE114C6C1D724A75C0395137AA397803 5425E78D
de.			86400	IN	RRSIG	DS 8 1 86400 20240326050000 20240313040000 30903 . rmEyyU9c898VCnoP0s7pfhYbUpLNH9R8rcKvZf/0rNcrKKxky34eCi03 Iy6q+y714q2zK8sNkgNRMD/oK2H1sDEHM67k/s4I4DNonnlwbGYhrnkt h0xh+oytDKE8eL+R3A4vAo5xPPimKmaPDMyZkJTdk8FCuPac7RBq6xJv GHLahvWReCsmcZtOOpES1KG6bTr9JMXCUoaN/ts3ZbO9PCbVpmItOj4a oZOBngflR7/IGKw47HdqcoSh8W9cSypdID5u4BxQusupWXjJ68fZDFV8 vUMQnjkSYO45r9KCNHTsVDm5gMjCAiPG5pSBbYUoWG3Yyh83M51VX2U5 ZDEaZg==
;; Received 749 bytes from 192.33.4.12#53(c.root-servers.net) in 44 ms

merkle-fam.de.		86400	IN	NS	helium.ns.hetzner.de.
merkle-fam.de.		86400	IN	NS	oxygen.ns.hetzner.com.
merkle-fam.de.		86400	IN	NS	hydrogen.ns.hetzner.com.
tjlb7qbojvmlf1s6gdriru7vsms1lg16.de. 7200 IN NSEC3 1 1 15 CA12B74ADB90591A TJLCSJAT4LJTVO0TJNCRRDF6KF6ONEFB  NS SOA RRSIG DNSKEY NSEC3PARAM
gs69a4hsbbv1dt62p15siiamrf0moee8.de. 7200 IN NSEC3 1 1 15 CA12B74ADB90591A GS6CDV0P1DT5GRJ19NO7LO7NG97OTNES  A RRSIG
tjlb7qbojvmlf1s6gdriru7vsms1lg16.de. 7200 IN RRSIG NSEC3 8 2 7200 20240321164258 20240307151258 51303 de. E/TrJD64E37pe59tJcxcOwWKazKDvWfGw47u7iVhM6ydmahk9l+ZRO7Z fVHTD5K/swoYBEKOsrKh4TYng/CHymRj0nqGwFbkdjh4t4rqVBNVTuoN fED2SG4Zaynzhc5yScwpqYpLd+DEtHCUIsRoKVVGZE4D+KyGI1KXMHxV KG8=
gs69a4hsbbv1dt62p15siiamrf0moee8.de. 7200 IN RRSIG NSEC3 8 2 7200 20240325133659 20240311120659 51303 de. TEE0GLnqJnShHHTYTFG7Q+JM0rtWt9uR7hCfGb0GadqoIzebhRkKaSvH X0mByWiKNexylQWDVYe1FkMvRRYscbRY/IlhmVyl1mZuuSdCkZolbZJd 97MyWaFt5Z0xjjkTuzFYzqMGQx7UWNdXHkqsWAjhLDBFArib8JdOwwBi zVU=
;; Received 631 bytes from 77.67.63.105#53(l.de.net) in 79 ms

merkle-fam.de.		86400	IN	NS	keyla.ns.cloudflare.com.
merkle-fam.de.		86400	IN	NS	joaquin.ns.cloudflare.com.
;; Received 101 bytes from 88.198.229.192#53(oxygen.ns.hetzner.com) in 70 ms

You can’t have it resolving to hetzner.com and then from there to cloudflare.com.
Please remove all non Cloudflare nameservers.

Take care.

2 Likes

Actually, you haven’t changed your nameservers at all, you just created NS records:

merkle-fam.de.          86400   IN      NS      helium.ns.hetzner.de.
merkle-fam.de.          86400   IN      NS      oxygen.ns.hetzner.com.
merkle-fam.de.          86400   IN      NS      hydrogen.ns.hetzner.com.
;; Received 132 bytes from 194.0.0.53#53(a.nic.de) in 28 ms

merkle-fam.de.          86400   IN      A       78.47.27.143
merkle-fam.de.          86400   IN      NS      keyla.ns.cloudflare.com.
merkle-fam.de.          86400   IN      NS      joaquin.ns.cloudflare.com.
;; Received 117 bytes from 2001:67c:192c::add:5#53(helium.ns.hetzner.de) in 24 ms

You need to replace the Hetzner nameservers with Cloudflare.

1 Like

Hi there,
thanx a lot - this site cf.sjr.org.uk was not in my mind.
The zone edit file of hetzner does not show any of the mentioned server of them in NS or SOA.
I removed the three servers already in their UI and the checked with the zone edit file.
I try a call with them to correct the zone. I hope that this was the error!
TIA
Thomas

$ORIGIN merkle-fam.de.
$TTL 86400
; SOA Records
@		IN	SOA	joaquin.ns.cloudflare.com. keyla.ns.cloudflare.com. 2024031300 86400 10800 3600000 3600
; NS Records
@		IN	NS	joaquin.ns.cloudflare.com.
@		IN	NS	keyla.ns.cloudflare.com.
; MX Records
@		IN	MX	10 mail
; A Records
@		IN	A	78.47.27.143
mail		IN	A	78.47.27.143
www		IN	A	78.47.27.143
; CNAME Records
autoconfig		IN	CNAME	mail
autodiscover		IN	CNAME	mail

The zone file is where you create NS records. So that’s the wrong menu. You need to find where to change the nameservers.

Edit: You should find that if you go to Robot → Domains.

2 Likes

Ah thanx! I try it. The Support of hetzner said, I should transfer the Domain to Cloudflare - but they don’t support .de :slight_smile:

TIA
Thomas

OK, that was the reason I didn’t see - merkle-fam ist now active :slight_smile:

Thomas

2 Likes

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