> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.squarecloud.app/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Why hasn't my domain propagated yet? (DNS)

## 1. The Time Factor: The 24-Hour Window

The most common reason for a domain "not working" is simply time. When you change the **Nameservers** at your provider to point to Cloudflare, this information needs to be replicated by all internet service providers (ISPs) across the globe.

* **Estimated Time:** Although it often happens within a few minutes, full propagation can take **up to 24 hours**.
* **Tip:** Do not repeatedly change settings during this period, as each modification can restart the propagation cycle on some servers.

---

## 2. Common Configuration Errors

Often, the problem is not propagation itself, but a technical error in data entry. Here are the most frequent cases:

### Inconsistency Between Root Domain and Subdomain
This is the most common error:
* **The Error:** You register the root domain on Square Cloud (e.g., `yoursite.com`), but on Cloudflare or at your provider, you created a record for the `www` subdomain (e.g., `www.yoursite.com`).
* **The Solution:** Make sure that what was entered in Square Cloud's **Network** tab matches exactly with the **Name** field of your Cloudflare record. If you want to use the domain without "www", use the `@` symbol in Cloudflare's Name field.

### Conflicting CNAME Records
If you previously pointed the domain to another hosting service, make sure you have deleted the old **A** or **CNAME** records. Having two different destinations for the same domain name will cause instability or access errors.

---

## 3. Local Cache: The Invisible Villain

Sometimes, the domain has already propagated worldwide, but your computer or router still "remembers" the old route (or lack thereof).

* **Browser Cache:** Try accessing the site in an **incognito window** or through another browser.
* **Windows/Mac Cache:** Your operating system stores DNS resolutions. You can flush this by opening the terminal and typing:
    * On Windows: `ipconfig /flushdns`
    * On Mac: `sudo killall -HUP mDNSResponder`
* **Mobile Network:** A quick way to test if it's your router's cache is to try accessing the site using your phone's **4G/5G data**, disconnected from Wi-Fi.

---

## 4. How to Diagnose with Precision

Don't guess whether the domain worked. Use technical global verification tools:

1. **DNS Checker:** Access the [dnschecker.org](https://dnschecker.org/) website.
2. **Enter your domain** and select the **CNAME** type.
3. **If most locations** display a green checkmark with the correct address, the problem is likely your local cache.

---

## Conclusion

If you have reviewed the records (CNAME and TXT), ensured that the domain on Square Cloud matches the one on Cloudflare, and waited a reasonable amount of time, your application should be online soon. If the error persists after 24 hours, double-check if Cloudflare's **Nameservers** were saved correctly at your original provider.