For a domain portfolio, DNS determines where website, sales-page and email queries are directed. It does not establish ownership or make an offline domain available to register. Understanding the settings is useful when acquiring, parking and handing over names.
Keep DNS work separate from registrar ownership changes. A nameserver edit changes the service route; transferring the registration changes who controls the name under the relevant process.
Record the current service arrangement
Identify the delegated nameservers and the provider actually serving the zone. The registrar panel may contain DNS settings that are inactive because another provider is authoritative.
RFC 1034 describes the DNS hierarchy and cached resolution model. A resolver may already hold usable information, so it does not necessarily contact every level for every query.
Our beginner’s DNS guide explains the record types. Not every registered name has an address record or one corresponding IP address.
Choose the records needed for the intended use
A and AAAA records provide IPv4 and IPv6 addresses. CNAME creates an alias, while MX identifies mail exchangers. TXT records can support verification and authentication, and NS identifies authoritative nameservers.
Cloudflare’s record reference explains common uses. A CNAME is not a browser redirect to a different URL. Use a hosting or sales-page provider’s instructions for the service being configured.
For a portfolio sale page, avoid changing unrelated email settings simply because a new lander requires an address record. Record each intended function before applying bulk edits.
Manage caching and provider changes
A record’s TTL affects how long resolvers can cache it. Cloudflare’s management documentation describes that setting. Lowering a value does not rewrite copies already cached under an older TTL.
Prepare the new zone before changing delegation where the provider’s process allows. Check relevant website, mail and verification records rather than copying unexplained settings indiscriminately.
If DNSSEC is involved, coordinate signing keys and parent DS information using the providers’ documented procedures. RFC 4033 explains authentication and integrity; DNSSEC does not provide confidentiality. Inconsistent chain information can disrupt validation.
Verify the result beyond the dashboard
Inspect public answers for the exact names and record types you changed. Then test the website or email function. A correct DNS answer does not establish that hosting, certificates or the application work properly.
Our site assessment guide covers that wider review. Record the date and expected result so later checks have a baseline.
Prepare a clean handover record
Agree whether the buyer receives DNS service arrangements or only registration control. Explain settings that support included services and identify any accounts outside the sale.
After completion, remove stale sale listings and update the inventory without making unauthorised changes to the buyer’s setup. Our management guide helps keep control, service and transaction records distinct.
Reliable DNS administration supports a clear transaction. It does not by itself raise the name’s value or guarantee uptime and profitable resale.