Sign in

Pointing My Domain At A CDN: Www Is Fine, Apex Loads The Old Site

Solvedcnamednsdomains6 replies · 396 views · started
Reply
Accepted solution by Farah Ferreira — lol same thing happened to me check what teh apex currently resolves to: dig A example.com +short and compare with dig CNAME…
  1. Kofi C.
    @kofic744

    My analytics showed a strange drop and when I checked, the bare domain loads the old site. The www version is fine.

    This site can't be reached

    This site can't be reached
Check if there is a typo in my-shop-site.example.
If spelling is correct, try running Windows Network Diagnostics.
DNS_PROBE_FINISHED_NXDOMAIN

    im using a budget registrar and pointing the site at a CDN. I think theres still an old A record from the previous host but Im scared to delete things I dont understand... could someone explain how apex and www are supposed to be set up?? A short explanation of what each record is supposed to do would help a lot.

    9
  2. Farah Lund
    @rusty_gremlin

    hmmm does my host's zone editor offer ALIAS, ANAME or flattening anywhere in the record types?? ??

    3 0 helpful
  4. Lars
    @lars_uplink

    lol same thing happened to me the DNS rules don't allow a CNAME at the zone apex cuz teh apex already holds SOA and NS recrods. That's why ur registrars DNS panel rejects it. You need either a provider feature that fakes it (ALIAS, ANAME or CNAME flattening) or plain A/AAAA records pointing at teh IPs ur host documents for apex domains. fingers crossed 🤞

    2 0 helpful
  5. Farah Ferreira
    @nightgarage-3lq
    Accepted solution

    lol same thing happened to me check what teh apex currently resolves to: dig A example.com +short and compare with dig CNAME www.example.com +short 😤 A leftover A record from an old host or a default parking IP from the registrar explains parked pages and old sites immediately. Delete those once the correct records are in place.

    6 5 helpful
  6. Diego
    @diegok342

    Honestly, for a simple site i'd make the apex the primary and drop www entirely. Fewer names, fewer certificates, fewer things to break. just my 2 cents

    2 0 helpful
  7. Kofi C.
    @kofic744
    in reply to @nightgarage-3lq

    @nightgarage-3lq wowww ok adding the apex as a custom dmoain on the host fixed the certificate warning instantly. such an easy thing to miss.

    4 0 helpful

Reply to this topic

Sign in or create an account to reply.