Images are AI-generated editorial illustrations, not documentary photographs or verified product screenshots.
DNS management begins with ownership and an inventory
DNS management is the maintenance of the records that tell other systems how to find services associated with a domain. Cloudflare describes DNS records as instructions held by authoritative DNS servers, including address and other service information. A website owner should know which provider controls the authoritative zone and who can approve changes. Domain registration, website hosting and email hosting may be handled by different organizations.
Identify what each existing record supports
Inventory website addresses, mail routing, verification records and service-specific entries before changing anything. A records hold IPv4 addresses, while AAAA records hold IPv6 addresses; other record types serve different purposes. Record the hostname, type, value, TTL and the service that depends on it. Do not delete an unfamiliar record because it looks old, as it may support mail authentication or a connection that is not obvious from the homepage.
Make one planned change at a time
Capture the current zone and prepare an approved rollback value before editing. Coordinate with the relevant host or service owner rather than copying values from another domain. Understand whether a provider proxies traffic or serves ordinary DNS for a particular record. Keep API tokens and account recovery secrets outside operating notes. Delegated, limited access is preferable to handing out a domain account’s full credentials casually.
Account for caching and validate at the right level
A changed record may coexist with cached answers until the relevant caches expire. Test the authoritative answer and the public result, then check the actual service rather than stopping at a successful lookup. A correct address does not guarantee that the web server, certificate or email service is configured properly. Record when the change was made and the evidence used to confirm that the intended route is working.
Maintain the zone as part of routine operations
Review records when services are added, moved or retired, and keep the ownership inventory current. Protect the registrar and DNS accounts with appropriate authentication and renewal controls. Confirm that a migration plan includes email and third-party services, not merely the website. If a record change causes an unexpected outage, stop adding speculative changes, compare the recorded before-and-after values and involve the responsible provider.
Common questions
Does changing web hosting automatically update every DNS service? No; identify and coordinate the required records. Does a successful DNS lookup prove the website is healthy? No; test the application too. Should every record use the same TTL? Choose values in the context of the service and provider guidance rather than applying a universal number.
Sources and further reading
cloudflare.com: dns soa record
Related reading
Writing a Freelance Handover Document Clients Can Use
Building a Reusable Website Maintenance Checklist
DNS AAAA Records: Check IPv6 Reachability Before You Publish