A records publish IPv4 destinations and AAAA records publish IPv6 destinations for a hostname.
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.
Key information
| A | Maps a hostname to an IPv4 address such as 192.0.2.10. |
|---|---|
| AAAA | Maps a hostname to an IPv6 address such as 2001:db8::10. |
| Root or apex | Often entered as @ or left blank, depending on the DNS control panel. |
| www | Usually a separate record or CNAME; it is not automatically covered by the root record in every DNS service. |
Before you start
- Confirm that you are authorised to manage the domain and identify its authoritative DNS provider.
- Export or record the complete current DNS zone and previous TTL values before making changes.
Step-by-step
- Confirm the public address supplied by the destination service and whether both IPv4 and IPv6 are supported end to end.
- Open the authoritative DNS zone and create the A record for the required hostname.
- Create an AAAA record only when the destination is correctly configured and reachable over IPv6; a broken AAAA record can take precedence for some visitors and certificate checks.
- Set an appropriate TTL, save once and query the authoritative nameservers directly.
- Test HTTP and HTTPS for the root and www hostnames separately on both address families.
Confirm the result
- Public queries return only addresses that actively serve the intended hostname.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| IPv4 works but some users cannot connect. | A stale or incorrect AAAA record directs IPv6-capable clients elsewhere. | Correct or remove the AAAA record and verify IPv6 before publishing it again. |
| The DNS panel rejects @. | That provider represents the zone apex with a blank field or the full domain. | Follow the interface convention and confirm the resulting fully qualified name before saving. |
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
- Manage DNS records
- A, AAAA, CNAME, MX and TXT records explained
- Check DNS with dig, nslookup and public resolvers
- Enable a free Let’s Encrypt SSL certificate
- Create and troubleshoot a CNAME record
Last reviewed: 2026-07-18.
