A CNAME makes one hostname an alias of another hostname; it must not be confused with a URL redirect.
Applies to: Nameservers and DNS records
DNS tells internet services where to find a website, mail server or other service. Changes can be technically correct yet appear inconsistent for a time because recursive resolvers cache earlier answers until their TTL expires.
Before you start
- Obtain the exact target hostname from the destination provider, without adding an IP address or web path.
Step-by-step
- Choose the alias hostname, such as www or verify, and confirm it is not already used by A, AAAA, MX or another conflicting record.
- Enter the provider's target as a hostname. Add a trailing dot only if the DNS interface requires it; otherwise verify that the panel does not append your domain twice.
- Do not create a CNAME at the zone apex unless the DNS provider explicitly supports a flattened or ALIAS-style equivalent.
- Save the record and query it publicly, following the CNAME chain until an address is returned.
- Test the destination application because DNS success does not prove that the target service recognises your custom hostname.
Confirm the result
- The alias resolves through the intended CNAME chain and the application serves the correct site or verification response.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The result becomes target.example.com.yourdomain.tld. | The interface treated the target as relative because a fully qualified name was not indicated. | Use the provider's documented format or a trailing dot where required. |
| The browser shows the provider's default page. | DNS is correct but the custom domain has not been added or verified at the provider. | Complete the provider-side domain connection and SSL process. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The full domain name
- The current and intended registrar or nameservers
- Any registry or transfer error shown
- Whether website or email service is currently live
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- A, AAAA, CNAME, MX and TXT records explained
- Manage DNS records
- Point a domain to Website Builder or another service
- Create and troubleshoot A and AAAA records
- Register child nameservers and glue records
Last reviewed: 2026-07-18.
