Awaiting Netlify not refreshing after more than 24h

Support
,
1

Hi everyone, I have moved a website from siteground to netlify and the awaiting netlify dns does not refresh. It has been more than 24h and I’m starting to think something is wrong and its not just propagation. I also looked with online dig tool and I see there are no A/CNAME records. I have removed the domain twice and it still says the same thing. The MX records and Google Verification have propagated successfully as the email service works fine (it didn’t before)

Screenshot 2024-09-30 at 14.55.10
Screenshot 2024-09-30 at 14.55.102812×1360 280 KB

Website link is https://bluesheepbooks.netlify.app/

Could you please assist me with this? Thank you!

3

Does someone knows a fix? Please I need an answer because my client is not happy

4

hey @Maccabro it looks like issue where an A Record was added then deleted which broke the NETLIFY Record. We ran a backfill on our side, and it looks like the site is up and running now.

5

Hi! Thank you for replying. Indeed the site is up but only for https:// version. The www is still awaiting

6

Hi, it can take up to 48 hours to propagate when this time has passed and if you are still seeing this issue please write back in.

7

I understand. Thank you very much both of you!

8

Hi, @Maccabro. There was still an issue on the Netlify side and that issue has been corrected now. The www subdomain is also working correctly now (with SSL and redirecting to the apex domain):

$ curl --compressed -svo /dev/null --stderr - https://www.bluesheepbooks.com/  | egrep '^(<|>)'
> GET / HTTP/2
> Host: www.bluesheepbooks.com
> User-Agent: curl/8.7.1
> Accept: */*
> Accept-Encoding: deflate, gzip
>
< HTTP/2 301
< content-type: text/plain; charset=utf-8
< date: Wed, 02 Oct 2024 21:05:30 GMT
< location: https://bluesheepbooks.com/
< server: Netlify
< strict-transport-security: max-age=31536000
< x-nf-request-id: 01J97GTS1XATJ6CWXCERER1HET
< content-length: 42
<

Again, there was still an issue at Netlify and that issue has been fixed now.

1 Like
11

Hi @luke, thank you for looking into the issue and also for fixing it further. Its all working as expected now. Have a great everything