How do you buy a domain and connect it to your app?
Register the name in an account you can recover. Find the DNS service that answers for it, then use the web host’s instructions to connect your site. If email already works on that domain, keep its records in place while you change the website.
Who controls the name, the records and the website?
The registrar keeps the registration for the name. The DNS service publishes the instructions that tell visitors and mail systems where to go. The web host runs the site people open. One company can handle several of these jobs.
Start with the domain’s renewal email or registrar account. Then look for the nameservers listed for that domain. A nameserver is a computer that answers DNS questions. These names identify the DNS setup you should check before editing records. Confirm the domain is present in that provider’s account and that you can see the current records.
You can look up public registration data if you don’t know the registrar. That can help identify the company to contact. Some contact information is hidden from public lookup, so use the account and its registrant details to confirm who controls the registration.
What should you check before buying or renewing a domain?
Check what the exact name costs to register today, renew for another year and transfer in if you move it. The ending, such as .com, changes the price. A name marked premium can have a different price from the standard list.
Keep the account under the control of the person or business responsible for the domain. Use an account recovery address you can still open if this domain stops working. Check the renewal date, whether auto-renew is on and whether its payment method is current.
| Price | When it applies |
|---|---|
| Registration | When you register the name. Check first-year offers, eligibility and fees. |
| Renewal | When you keep the name for another term. Use this to plan the ongoing cost. |
| Incoming transfer | When you move the registration to that company. Check whether it extends the term for your domain ending. |
Compare tools
Scroll the table sideways to read every column.
| Tool | What you can manageDomain registration, DNS hosting or both. | Where you edit recordsWhich account controls the records people use. | What changes the billWhat to compare when buying, renewing or moving. | What you check before a moveWhat you need to keep control of the name and records. |
|---|---|---|---|---|
| Porkbun | Register or renew a domain. Use Porkbun’s DNS or choose a separate DNS service. | Use Porkbun’s DNS Records screen when its nameservers are active. | Compare standard, promotional and premium rates by domain ending. Porkbun lists registration, renewal and incoming transfer separately. | Save the current records before moving. Check eligibility and request a transfer code if you’re changing registrars. |
| Namecheap | Register or renew a domain. BasicDNS is the default for a Namecheap registration. | Open Advanced DNS for BasicDNS, FreeDNS or PremiumDNS. Use the active DNS provider if it’s elsewhere. | The first-year offer and regular renewal can differ. Check fees and any optional PremiumDNS subscription separately. | Before changing nameservers, prepare the destination records and check any DNSSEC settings. A registrar transfer also needs its own authorization. |
| DNSimple | Use it as a registrar, a managed DNS service, or both. | If your domain is registered elsewhere, point its nameservers to DNSimple to use its hosted records. | Domain fees are separate from hosted DNS charges. Check monthly hosted zones and DNS lookups. | Export the records. Recreate any provider-specific features and plan the DNSSEC change before switching. |
How can you plan one website change without touching email?
Use example.com on paper or in a local note. It’s reserved for examples. These are made-up records for practice. Leave the domain’s actual DNS and every account alone. Use the made-up record table below to plan how you would move the site at www. The address www.example.com has its own record, separate from example.com.
- Name the one thing that should changeThe sample host says to point www to new.example.net. Write down www, the record type CNAME, the old value and the replacement. A CNAME points one name at another.
- Mark the records that should stayKeep the bare example.com web record, the mail route and the sending-domain record exactly as shown in this exercise. Your instructions change only www.
- Write your before and after checksWrite that www should reach the new site, while the bare name and email should behave as before. In a real approved change, check the new site and its HTTPS certificate and use mailboxes you control for any mail checks.
- Write how you would undo itKeep old.example.net as the previous value for www. If the real site’s check fails, you need that value and the old host still serving the site. A cached answer can take time to expire after any change.
| Name and type | Current value | Planned action |
|---|---|---|
| www CNAME | old.example.net | Replace with new.example.net |
| example.com A | 192.0.2.10 | Keep the address for the site without www |
| example.com MX | 10 mail.example.net | Keep the inbound mail route |
| example.com TXT | v=spf1 include:spf.example.net -all | Keep the sending-domain settings |
On a small screen, scroll the table sideways to read every column.
When does moving DNS risk breaking the website and email?
Changing nameservers changes who answers for the whole domain. Prepare the new DNS records before changing that setting. Bring over website, mail, verification and any subdomain records the app depends on.
Mail uses more than one record. MX tells other servers where to deliver incoming messages. SPF and DKIM help receivers check whether mail is authorized or signed. DMARC publishes what you ask receivers to do when mail fails its alignment checks. Keep the exact mail provider settings when moving DNS, including records on mail-related subdomains.
If DNSSEC is on, ask the registrar and DNS providers how to move it before switching nameservers. DNSSEC lets resolvers validate the answers. The registrar can publish a DS record that tells resolvers which signing key to trust. If it still points to the old key after the move, the website and mail lookups can fail for people using validating resolvers.
If you’re changing only the registrar, check whether the current DNS service will continue after the transfer. Prepare a replacement if the old registrar supplies DNS only while it keeps the registration. Keep your old records and known working service until the move has passed your checks.
How can someone recover the domain if you can’t sign in?
Keep a private record of the registrar, renewal date, active DNS service and who can sign in. Add a second sign-in check and keep its recovery method somewhere the responsible person can reach if the domain or phone is unavailable.
Keep a recent copy of the records and note what each service needs. If someone takes over the project, have them confirm they can sign in and renew it using the provider’s supported account process. Keep passwords, backup codes and transfer codes in the approved private place for those secrets.
If the name has already expired, check its status with the registrar and contact them promptly. A renewal or a paid restoration may be possible depending on the ending and stage. Even an expired domain you can still recover can interrupt the site and email.