Sign in

alias, aname, cname flattening... which fixes my a website builder setup?

Solvedcnamednsdomains5 replies · 186 views · started
Reply
Accepted solution by Wren Zhang — the DNS rules dont allow a CNAME at the zone apex because teh apex already holds SOA and NS records. thats why a budget registrar rejects…
  1. Jade P.
    @pixel_forge

    guys pls help moved my site to a website builder this weekend. www.mydomain loads perfectly. but type teh domain without www and it shows a parked page.

    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

    the host's docs say to add a CNAME for the root domain, but a budget registrar refuses and says a CNAME cannot coexist with other records... i don't want to lose visitors who type the short version... what's the correct way to handle this?? i'd love to understand teh why, not just copy another record from a forum.

    4
  2. Wren D.
    @wdemir

    registrar URL forwarding often only works over HTTP and has no certificate for HTTPS, sooo anyone visiting https://example.com gets a warning. Prefer pointing the apex at your host with A records and letting the host handle the redirect to www with a valid certificate.

    2 0 helpful
  3. Maya
    @mtanaka

    ok so for me it was the extension 🤦 swapped it and boom, fixed good luck man!

    1 5 helpful
  4. Jonas
    @jonasr139

    honestly just reset the default config and save yourself teh pain

    4 0 helpful
  5. Wren Zhang
    @wren.zhang
    Accepted solution

    the DNS rules dont allow a CNAME at the zone apex because teh apex already holds SOA and NS records. thats why a budget registrar rejects it. u need either a provider feature that fakes it (ALIAS, ANAME or CNAME flattennig) or plain A/AAAA records pointing at the IPs ur host documents for apex domains. good luck man!

    2 7 helpful
  6. Jade P.
    @pixel_forge
    in reply to @wren.zhang

    @wren.zhang removed teh mystery A record, added teh host's documented A records to the apex, and both versions work over HTTPS now. thx all!

    1 2 helpful

Reply to this topic

Sign in or create an account to reply.