DNS Records have been added, but site is still not live

Publishing help Project settings
1

Coming from Duda , this is my first webflow project. With all of my duda sites, sites go live almost instantly with the SSL generation finishing within the hour. And they have live chat so when I end up in a situation like I’m in now with an hour down and still no live site, I can get help right away to tell me how I’m being a moron. See screenshots and read only link - what am I missing that’s preventing my site from going live?

Screenshot 2024-06-27 083344
Screenshot 2024-06-27 0833442557×1506 330 KB

Screenshot 2024-06-27 081225
Screenshot 2024-06-27 0812252544×1515 428 KB

Here is my site Read-Only: LINK Webflow - householdenvironmental
(how to share your site Read-Only link)

2

I’ve also been been trying to click the “check status” buttons, and nothing happens.

3

Your site is active. You probably have cached DNS records on your local machine, or whatever DNS you are using in your IP config. You can look up how to clear your cache for your device/OS with your fav search engine.

4

Thanks, I was checking in incognito on a couple different devices, and both LTE and wifi - I think it just took time, as it is now showing live on my end. Stressful that it took a full hour - maybe I’ve just been lucky with the 30 duda sites I’ve launched, and should stick to launches after like 10pm for clients that already had a functioning live site to avoid even the risk of downtime

5

Always keep your previous service up and running for at least 48 hours when changing hosts.

  • Usually, DNS updates happen pretty fast. Imagine it’s like changing your address with all your friends. Some friends get the new address right away, but others might take a little longer.
  • The longest wait is usually 24 to 48 hours. After that, everyone knows about your new site!
6

I use Cloudflare so it’s always almost instant, but you can try and help things along by waiting a few minutes after a change and then Purging / Flushing all the big guys.

Cloudflare: 1.1.1.1 — the Internet’s Fastest, Privacy-First DNS Resolver
Google: ניקוי מטמון  |  Public DNS  |  Google for Developers
Open DNS: https://cachecheck.opendns.com/

Always purge you domain first so A records and then you CNAME, www. etc

Finally, remember to always clear the local DNS cache as that’s usually the problem for my clients if they don’t see something straight away.

macOS

  1. Open the Terminal application. You can find it in the Applications > Utilities folder or by searching for “Terminal” in Spotlight.
  2. Enter the following command and press Enter:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  1. You might need to enter your administrator password. After that, your DNS cache will be flushed.

Windows

  1. Open Command Prompt with administrative privileges:
  • Press Win + X and select “Command Prompt (Admin)” or “Windows PowerShell (Admin)”.
  • Alternatively, you can search for “cmd” or “Command Prompt” in the Start menu, right-click it, and select “Run as administrator”.
  1. Enter the following command and press Enter:
ipconfig /flushdns
  1. You should see a message confirming that the DNS Resolver Cache has been successfully flushed.

Linux

  1. Open your terminal application. This can usually be done by searching for “Terminal” or pressing Ctrl + Alt + T.
  2. The command to flush the DNS cache depends on the service your system uses. Here are a few common ones:For systems using systemd-resolved:
sudo systemctl restart systemd-resolved

3.For systems using dnsmasq:*

sudo systemctl restart dnsmasq

4.For systems using nscd:*

sudo systemctl restart nscd

If none of these apply, you can always try restarting your network service:

sudo systemctl restart NetworkManager