Domain not working: DNS propagation, wrong records or HTTPS?
Hosting & Domains September 15, 2026

Domain not working: DNS propagation, wrong records or HTTPS?

After adding records, waiting is not the answer to every problem. Separate domain registration, the active DNS provider, correct values, platform verification and HTTPS. Identifying the failing stage saves time and avoids changing records that already work.

Choose a platform and search for a domain on IT PLUS
On the IT PLUS domain connection page: choose your platform and search for a name. Interface captured on 15 September 2026.

Start with these checks

  1. Check registration, expiry and any registrant-verification notice.
  2. Identify the current nameservers. Did you edit the DNS provider those nameservers belong to?
  3. Compare the record type, name and value with the project’s current instructions.
  4. Check the root domain and www separately; one working does not prove the other works.
  5. Read the platform status and HTTPS error. Note the last change time so you do not keep resetting records without a reason.

How do you interpret the result?

ObservationPossible causeNext action
Authoritative DNS has the new value; some networks still see the old oneCached DNSAllow the TTL to expire and compare networks without repeated edits.
The active DNS provider does not have the valueWrong panel or unsaved changeUpdate the active provider with the required value.
The platform reports ownership verification failureMissing or incorrect TXTCompare the project-specific name and token.
DNS reaches the platform but HTTPS failsCertificate or domain setup is incompleteCheck the platform’s certificate status and error.
The website works but mail does not arriveMail records or provisioningCheck MX and mail provisioning; a working site does not prove email works.

How long does propagation take?

Results may appear within minutes, while cached values can persist for hours or longer depending on TTL, resolver caching and nameserver changes. A 24–48-hour estimate is not a fixed promise or a reason to wait when a value is wrong. Certificate issuance also has its own platform checks.

What should you send support?

  • The domain, platform and approximate time of the last change.
  • The error text or a screenshot with private information hidden.
  • Required record names and types, without passwords or account keys.
  • Whether the issue affects the website or email and whether multiple networks reproduce it.

Do not delete all records or randomly change nameservers. Keep a copy before editing, and review DNSSEC or CAA with support when the error points to them.

References:

DNS TTL · Lovable domain status

Choose your next step

Contact us with your findings

Prepared and reviewed by IT PLUS. Service pages, application code and the linked documentation were reviewed on 15 September 2026. example.com is illustrative. Button labels may change as platforms update.

See registration and renewal prices before you book

.com

First year
$ 13.31
One-year renewal
$ 13.74

.net

First year
$ 15.39
One-year renewal
$ 15.39

.shop

First year
$ 1.91
One-year renewal
$ 42.19

Current one-year prices for standard names. Premium names have different prices; your name and term are priced before payment. Renewal prices and exchange rates may change.

View all extensions and prices

Leave a Comment

Comments (0)

No comments yet. Be the first to comment!