The records you should recognise
| Type | Purpose |
|---|---|
| A | Name to IPv4 address |
| AAAA | Name to IPv6 address |
| CNAME | Name to another hostname |
| TXT | Verification and text policies such as SPF |
| MX | Mail destination; lower priority number is preferred |
| NS | Authoritative nameservers for a DNS zone |
TTL tells recursive resolvers how long they may cache an answer. “Propagation” is usually old cached data expiring at different times.
GoDaddy-to-ESA case study
- Export or record every current DNS entry at GoDaddy, especially MX, TXT and verification records.
- Add the domain to ESA and choose the access method shown by the current console—NS delegation or CNAME.
- Recreate required records before changing nameservers. Do not lose email-related MX/TXT records.
- Lower relevant TTLs before the migration if your current provider permits it, then wait for the old TTL period.
- Change only the exact GoDaddy nameserver or record values ESA provides.
- Verify the authoritative NS, web records, email and HTTPS from multiple resolvers before deleting old configuration.
Risk warning: an incorrect nameserver change affects the entire DNS zone and can interrupt the website and email. Keep a record of the previous settings and make one controlled change at a time.
Official Alibaba Cloud: Add a domain to ESA →Verify instead of guessing
nslookup -type=NS hafizrich.com
nslookup -type=A hafizrich.com
nslookup -type=MX hafizrich.comDifferent resolvers may return different cached answers until their TTLs expire. Some resolvers may retain data longer than the configured TTL.
Official Alibaba Cloud: DNS record types →