ESDomain editorial team · Reviewed 2 November 2026
Get the settings from your host
Open your hosting provider’s domain connection instructions before editing DNS. Identify the record name, its type and its destination. An IP address, a server hostname and a full website URL are different values. Copy the value intended for each field, keeping the instructions available so you can compare the saved result against them.
Save the existing records and identify the authoritative DNS provider. If your domain uses external nameservers, changing a different zone will not change public answers. ESDomain’s integrated editor serves domains using our nameservers. Establish which provider is authoritative before troubleshooting a website that has not responded to an apparent DNS change.
Separate the root name from www
The @ symbol represents the root domain in many control panels: example.es. The name www represents www.example.es, which is a separate entry. Check both against your host’s instructions. Connecting one does not necessarily configure the other or redirect visitors to your preferred address. That redirect belongs in the website or hosting configuration.
Use a relative record name in ESDomain’s editor: @ or www as appropriate. Do not include https or a page path. A records point to IPv4 addresses, AAAA records use IPv6, and CNAME records point to another hostname. A plausible-looking value from an unrelated guide will not connect your particular hosting account.
Resolve conflicts before saving
Look for an existing record with the same name before adding another. Editing the intended entry is often clearer than creating an unexplained duplicate. A CNAME must not coexist with other data at that same name. Keep the original value when replacing a record so you can review or reverse the specific change if needed.
ESDomain’s editor does not accept a CNAME at the @ root. If a platform asks for one, check its compatible alternatives or recommended DNS service. Some providers offer special handling for that situation; it is not equivalent to adding an ordinary CNAME in every panel. Leave MX and email-related TXT records untouched when changing only the website.
Check the website and certificate
After saving, visit both the root address and www. Confirm they show the right project, that the host recognises the domain and that HTTPS covers the addresses in use. Correct DNS does not itself install a website or prove that the hosting platform has completed its own domain verification and certificate provisioning.
If results vary, record which entry changed and when. Caches can retain earlier answers for a while. Avoid repeated conflicting changes without checking the authoritative response. When asking support for help, include the domain, record name, record type and observed error. Keep account passwords and private keys out of the ticket.