Why this happens
After changing DNS records, your browser, operating system or router, still has the old DNS values for your domain cached. So, when you type in your domain in your browser, it will try to resolve it by visiting the the old DNS record/NS server. This happens with any kind of DNS changes, be it connecing your domain to LovableHTML, Clouflare or any other proxy. This cache can persist for minutes to days, depending on your domain's TTL (Time To Live) settings.
The result: you see "site cannot be reached", 503/1001 or SSL error in your browser but everyone else (or you in incognito mode) sees your site working perfectly.
How to verify it's a DNS cache issue
- Try incognito/private mode — For most users, this is enough to see the live site. if it works there, it's your browser cache
- Try a different device — if it works on your phone - with WiFi off, using cellular, it's your local network cache
- Ask a friend to check — if it works for them, your DNS is stale, or ask from me aki@launchfast.shop. I will send you a screenshot.
- Use an online tool — sites like dnschecker.org show what DNS servers worldwide see
How to fix it
There is nothing to fix here, really. Your site is live and no need to do anything on your end. It's just the stale DNS cache on your machine which will fix itself in a few mins to an hour. Your browser/network will start loading your site as normal by itself.
Option 1: Wait it out (easiest)
DNS propagation typically completes within 20mins to 60mins depending on your domains previously set TTL settings. The latest, you will see the change within a couple of hours.
Option 2: Flush your DNS cache
On macOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
On Windows:
ipconfig /flushdns
On Linux:
sudo systemd-resolve --flush-caches
Option 3: Restart your router (not necessary for 99% of cases)
Your router also caches DNS. A simple restart clears this cache.
Option 4: Use a different DNS server temporarily
Change your DNS to Google (8.8.8.8) or Cloudflare (1.1.1.1). These typically have shorter cache times.
Pro tip: Before making DNS changes, lower the TTL to 60 seconds a few hours in advance. This makes future propagation much faster.
