Updated October 9, 2026.
A domain name is a readable name such as example.com. Your business can use it for a website and email, but registering it does not automatically provide either service. Understanding that separation helps you compare quotes and make changes without disrupting things that already work.
Four services that may be in different accounts
| Part | What it does | What to record |
|---|---|---|
| Domain registration | Maintains your registration for the name | Registrar, account owner, renewal date, and recovery method |
| DNS hosting | Publishes records that connect the name to services | Authoritative nameservers, DNS provider, and a current record inventory |
| Website hosting | Serves the website or application | Provider, plan, domain configuration, and support contact |
| Email hosting | Receives and sends business email | Provider, administrator, and required DNS records |
One company may provide several of these services. They can also be separate. Do not assume the account where you pay for the domain is where every DNS change must be made.
How the name connects to a service
In blog.example.com, com is the top-level domain and blog is a subdomain of example.com. Registration structures differ across extensions, so this example is not a rule for every name.
DNS lets software look up records associated with names. A lookup can return an address or information used to locate another service. Results may be cached, so not every visit starts a new lookup from scratch. Mozilla’s domain-name introduction explains the basic structure and registration model.
Registration gives you the right to use the name for a renewable term, subject to the registration agreement. Treat renewal and account recovery as business responsibilities rather than leaving them with a former employee or an inaccessible contractor account.
Choose a name you can use consistently
Say the proposed name aloud and ask someone to type it. Check whether it is easy to confuse with another business or another spelling. A short name can be convenient, but an arbitrary character limit is less useful than a name customers can recognize and communicate.
Choose an extension that fits your business and check its eligibility rules, availability, and renewal cost. Do not assume that an unfamiliar extension is inherently unprofessional or that putting a keyword in the name guarantees search visibility.
Before spending heavily on a name or brand rollout, resolve any uncertainty about using that name. Availability at a registrar is not a clearance of every possible naming conflict.
Compare registrars on the terms that matter
Instead of choosing from a dated sale-price table, compare the exact domain at checkout and on the renewal schedule:
- First-term price, renewal price, registration length, and any premium-domain pricing.
- Included privacy features and any extension-specific exceptions.
- Multi-factor authentication, account recovery, and access for a developer without sharing the owner’s password.
- Support channels and hours you can actually use.
- Whether you must use the registrar’s DNS service and whether that fits your setup.
- Transfer, expiration, and restoration terms.
Save the relevant terms with your account inventory. Introductory and renewal prices can differ, and an at-cost pricing model does not mean the underlying registry price can never change.
Use a business-controlled account and current contact details. Enable multi-factor authentication, keep recovery information in an appropriate secure location, and set a second renewal reminder even if auto-renew is enabled.
What about registration privacy?
Do not assume every registrant’s full contact information is publicly visible, or that a privacy feature makes registration anonymous. ICANN’s RDAP guidance explains access to registration information. Its Registration Data Request Service concerns requests for nonpublic data. The ICANN lookup service can help identify a registrar and available registration details.
Review the provider’s disclosure for your extension, including what is public and how contact requests are handled. Privacy features do not replace accurate account information or control of the registration.
DNS records you are likely to encounter
The DNS record reference explains the record types below. Use the exact names and values supplied by your website or email provider; this table describes their roles, not a configuration to paste into your account.
| Record | Purpose |
|---|---|
| A | Associates a name with an IPv4 address |
| AAAA | Associates a name with an IPv6 address |
| CNAME | Makes a name an alias of another name, subject to DNS/provider constraints |
| MX | Identifies mail servers and their priorities for receiving email |
| TXT | Holds text used for purposes such as service verification and email authentication |
| NS | Identifies authoritative nameservers for a DNS zone |
| CAA | Specifies which certificate authorities may issue certificates for the name |
A CNAME is not a web redirect: it does not tell a browser to change the address in its address bar. Similarly, an MX record is not a website address. Copying a sample value such as mail.google.com is not a substitute for your email provider’s setup instructions.
We use example.com here because IANA reserves it for documentation. Do not use sample domains or private-network addresses from tutorials as your public hosting configuration.
Connecting a website without breaking email
Before changing anything, identify the authoritative DNS provider and save the existing records. Ask your website host for the required settings and distinguish a change to a few web records from moving the entire DNS service.
- Confirm the host is configured to serve your domain and explain any verification steps.
- Preserve the email, authentication, and other service records that still apply.
- If moving nameservers, prepare the destination zone before switching; ask the provider how to handle DNSSEC if enabled.
- Make the agreed changes and test both the main domain and
wwwif used. - Confirm HTTPS works, and test inbound and outbound email with another account.
- Keep the old setup available until you have checked the transition and know how to recover.
DNS caches and provider processing affect when changes become visible. Do not treat “wait 48 hours” as a fix for an incorrect record. If results disagree, verify the authoritative answer and the provider’s configuration before making more changes.
Transferring a registration is a different task
You can often change website hosting without changing registrars. If you do want to transfer the registration, first check the current registrar’s process and your domain’s eligibility.
For applicable generic-domain transfers, ICANN’s registrant transfer FAQ describes authorization codes and transfer restrictions, including locks related to recent registration, transfer, or registrant changes. Do not assume the same process or timing applies to every country-code domain.
Arrange DNS continuity before starting. A registration transfer is not a guarantee that the old provider will continue hosting your DNS or email. Confirm what stays active, preserve records, and avoid combining unnecessary service changes into one transition.
Keep a small domain inventory
Record the domain, registrar, renewal date, DNS provider, website host, email provider, account owner, and recovery contact. Keep passwords and recovery codes in your secure credential system rather than an ordinary shared document.
Review that inventory when staff or suppliers change. Knowing who controls each part makes the next website project much easier to manage.