Updated
Start with your website provider’s instructions. A browser address or an online example cannot replace the DNS values supplied by that provider.
Check where DNS is managed
Check the current nameservers. If DNS is external, make changes in that service’s active zone. A zone retained elsewhere does not control the domain merely because its records remain visible.
Save current values and identify website, email and service verification records. Connecting only a website does not require deleting existing MX or TXT records.
Use the requested record type
A maps a name to IPv4; AAAA to IPv6. CNAME points to another name, without https:// or a page path. MX identifies an incoming email server and priority. TXT publishes text, including verification data.
In the editor, @ represents the domain itself and www a subdomain. A CNAME must not conflict with other data at the same name; do not add one at the root without an explicitly supported solution.
Recognize examples and check the result
Syntax examples only: A, host @, value 192.0.2.10; CNAME, host www, value destination.example.com; MX, host @, value mail.example.com, priority 10. These values do not connect your service; replace them with its actual instructions.
- Check the full hostname preview, type and value.
- Review the proposed change and preserve data unrelated to the website.
- After applying it, check both the bare domain and www, then test email if the domain uses it.
Understand caching and HTTPS
Time to live, or TTL, describes how long a DNS answer may be cached. An old answer can remain in use until its cache expires; lowering TTL now does not erase already cached answers.
Correct DNS alone does not create an HTTPS certificate. Add the domain in the website service too and check its certificate there. If it fails, record the tested name and exact error before changing other settings.
Official references
These references explain the cited rules and principles. For your own domain, frdomain.fr support remains your point of contact.