Waiting on DNS propagation since ~36 hours

Support
1

Hey everybody,

after successfully handing over my domain to the control of Netlify I don’t get a letsencrypt certificate. It’s been ~36 hours now.

https://raesener.netlify.com works of course
https://raesener.de doesn’t work

I’ve also deleted the site altogether and started a new one with same settings, didn’t help so far. The domain had an working letsencrypt certificate from my own hosting - maybe that’s an issue?

Thx for any hints.

I can’t reach anyone from Netlify, do I have to upgrade to a paid plan?

2

to give some updates, I’ve now manually revoked the existing certificates for the domain via certbot and recreated the site once again.

right now I get

We could not provision a Let’s Encrypt certificate for your custom domain.

besides the custom domain ist handed over again or rather still to netlifyDNS. I’ve set the nameservers to the ones from netlify.

If I click on verify dns I get a success message and the button to provision a new certificate, which I did.
No I get again:

Waiting on DNS propagation

Any hints appreciated.

3

Hi, @elmcrest, the domain isn’t using Netlify DNS. The name servers used can be found in the WHOIS data for this domain:

$ whois raesener.de | egrep -i "(nserver|name server)"
nserver:      A.NIC.DE 194.0.0.53 2001:678:2:0:0:0:0:53
nserver:      F.NIC.DE 2a02:568:0:2:0:0:0:53 81.91.164.5
nserver:      L.DE.NET 2001:668:1f:11:0:0:0:105 77.67.63.105
nserver:      N.DE.NET 194.146.107.6 2001:67c:1011:1:0:0:0:53
nserver:      S.DE.NET 195.243.137.26 2003:8:14:0:0:0:0:53
nserver:      Z.NIC.DE 194.246.96.1 2a02:568:fe02:0:0:0:0:de
Nserver: ns.inwx.de
Nserver: ns2.inwx.de
Nserver: ns3.inwx.de

If you do a DNS lookup it shows the Netlify DNS servers:

$ dig raesener.de NS  +noall +answer

; <<>> DiG 9.10.6 <<>> raesener.de NS +noall +answer
;; global options: +cmd
raesener.de.		21599	IN	NS	dns1.p07.nsone.net.
raesener.de.		3599	IN	NS	dns4.p07.nsone.net.
raesener.de.		21599	IN	NS	dns2.p07.nsone.net.
raesener.de.		21599	IN	NS	dns3.p07.nsone.net.

However, those records above are never used because they are not the authoritative name servers for this domain.

Please contact your domain registrar to get their instructions about how to change the authoritative name servers for this domain.

If there are other questions about this, please let us know.

4

Hey @luke,

thx for the reply, fixed. INWX somehow has confusing instructions about changing the nameserver but with your hint, no problem at all.

 % whois raesener.de | egrep -i "(nserver|name server)"
nserver:      A.NIC.DE 194.0.0.53 2001:678:2:0:0:0:0:53
nserver:      F.NIC.DE 2a02:568:0:2:0:0:0:53 81.91.164.5
nserver:      L.DE.NET 2001:668:1f:11:0:0:0:105 77.67.63.105
nserver:      N.DE.NET 194.146.107.6 2001:67c:1011:1:0:0:0:53
nserver:      S.DE.NET 195.243.137.26 2003:8:14:0:0:0:0:53
nserver:      Z.NIC.DE 194.246.96.1 2a02:568:fe02:0:0:0:0:de
Nserver: dns1.p07.nsone.net
Nserver: dns2.p07.nsone.net
Nserver: dns3.p07.nsone.net 
Nserver: dns4.p07.nsone.net

OK, now I’m waiting again. Hopefully it works.

5

Ok, worked perfectly.
Little sidenote: why don’t you offer more obivous “pay to get support” options?

6

glad it’s working for you! At the moment, it’s not possible to add support-only as an add on, but, that’s definitely something to consider for the future.