Your business should be able to renew its domain, recover access to the registrar, and authorize DNS changes without relying on one employee or vendor. Your IT provider or web developer can handle the work day to day. The business should still know where the accounts are, who can act on its behalf, and what would break if a setting changed.
A useful first check: ask an authorized person to sign in to the registrar and the DNS provider and confirm they can see the domain in both places. Have them check the renewal date and recovery contacts without changing any live settings.
Identify who controls each part
- Registrar: The company you use to register and renew the domain. Check who is listed as the registrant, who receives notices, and who can approve changes.
- DNS provider: The service that publishes the records for your domain. Find the active nameservers and confirm which account manages the corresponding records.
- Website and email providers: The services that actually host your site and mailboxes. Record their support contacts separately, even if one vendor sends you a single bill.
ICANN’s registrant guide explains how the registrant and registrar relate and points to a lookup tool if you do not know the registrar. Use the registrar’s records to confirm your details; public lookup results can mask registrant information.
Confirm renewal and recovery belong to the business
Check that the registrant information reflects the business or the intended holder. Confirm the renewal date, billing contact, and payment method. If automatic renewal is on, still give someone responsibility for checking that it succeeds. Calendar the review early enough to resolve a billing or access problem.
Decide how an authorized person could recover the registrar account if the usual administrator were unavailable. Avoid relying solely on a mailbox at the domain you are trying to recover: if that domain stops working, the reset email might never reach you. Use a business-controlled recovery option that remains reachable, where the registrar supports it. Keep recovery secrets in your approved secure system, separate from the general handover notes.
Ask whether your registrar and DNS provider support named accounts and delegated roles. Give vendors the access needed for the work, and include the accounts in your MFA rollout. Document how the business would revoke vendor access after a handover.
Keep a DNS record you can hand over
Keep a dated export or inventory of your current records in an approved business location. Label which records serve the website, inbound mail, email authentication, subdomains, and third-party verification. The Cloudflare DNS record guide explains common types, including MX records used for mail delivery and records used to authenticate email.
Ask the person managing DNS to note which settings live outside a standard export. Examples include redirects, proxy settings, and any security settings a new provider would need to account for. A file of records helps someone rebuild the setup; it does not tell them which vendor supplied each value or how to verify that the service works.
Separate a provider change from a DNS change
Suppose a hypothetical Fort Worth contractor hires a new web developer. The job may only require pointing the website records at a new host. Moving the domain registration or replacing the nameservers adds work and can affect the office’s mail or a separate scheduling portal. Ask the developer to identify the exact changes and explain which existing settings stay in place.
For a larger change, agree on a time, who approves it, who can restore the previous settings, and what would trigger a rollback. Afterward, check the website at its usual addresses and have authorized staff test sending and receiving email and opening critical subdomains. If the provider will be changing, use the IT provider handover checklist to assign each step.
What to do if you cannot sign in
Gather your renewal invoices, the registrar name, and any agreements that identify who registered the domain. Ask the current account holder to arrange the handover through the provider’s process. If you cannot reach them, contact the registrar through its official support channel. ICANN’s registrant FAQ covers cases where a developer set up the account and explains why the registrar may need to verify who can act.
When changing registrant details and moving to a new registrar are both on the table, ask about transfer eligibility and the order of operations before acting. Requirements can differ by domain and registrar. Until there is a plan, keep existing DNS and hosting active so important services can keep running.
Put the answers in one place
Keep a short record of the registrant, registrar, renewal date, DNS provider, authorized administrators, and the location of your DNS inventory and recovery instructions. Review it when someone leaves or a vendor changes. Whether your team works in Fort Worth, Weatherford, elsewhere in West DFW, or remotely across the U.S., someone in the business should know where to start if that domain stops working.
If you are unsure who controls these accounts, bring your list to IronLink IT’s free Business IT Review. It’s a 20-minute conversation with a one-page summary of three priorities. No logins, scans, or system access are required.
Further reading
Related guides
Get a clearer picture of your business IT.
Start with a free 20-minute Business IT Review and a one-page summary of three priorities. No logins, scans, or system access required.
Request your free IT reviewFort Worth · Weatherford · West DFW · Remote support across the U.S.