Website, domain, DNS, and email: how the pieces fit together
See how a business domain, DNS records, website delivery, SSL, and email providers connect—and why changing one can affect the others.
Your domain is the shared label customers use for the website and business email. DNS is the directory that points different uses of that label to the right providers. The website and mailbox services are separate destinations. Understanding those roles makes migrations and troubleshooting much safer.
The domain is the registered name
The registrar records who controls a name such as example.com, subject to registry and account terms. Registration must remain current. The account should be business-controlled, protected by MFA where available, and monitored for renewal.
Registering a domain does not automatically create a website or mailbox. It creates the right to configure the name while the registration remains valid.
DNS publishes the directions
Nameservers identify where the domain’s DNS zone is managed. Records inside that zone point services to destinations. Website records commonly use A, AAAA, or CNAME types. Email delivery uses MX records. TXT records often carry verification and email-authentication policies.
Because all of these records can share one zone, replacing DNS carelessly while launching a website can interrupt email. Always inventory the current zone before changing nameservers.
The website is one destination
The website provider serves pages when a browser requests the domain. SSL/TLS certificates allow encrypted HTTPS connections and confirm that the responding service is authorized for the hostname. A managed deployment should connect the hostname, certificate, redirects, and monitoring as one launch task.
Read managed websites versus traditional hosting for the operational distinction.
Email is another destination
Google Workspace or another mail provider receives messages according to MX records. SPF, DKIM, and DMARC help receiving systems evaluate legitimate sending. The website host does not need to be the email provider, and moving the website should not require moving email.
Website forms may send through yet another provider. Their sending domain must be included in the authentication plan.
Changes travel at different speeds
DNS caches records for their configured lifetime. Providers also verify domains and issue certificates on their own schedules. Plan changes, lower cache lifetimes when appropriate, and preserve a rollback path. Avoid stacking a registrar transfer, nameserver move, website launch, and email migration into one uncontrolled event.
One owner, several specialists
Customers should know which account owns each layer, even when Doory coordinates the work. The Doory client portal remains the system of record for domain ordering and billing. Google controls Workspace. Cloud delivery serves the managed site. Clear ownership prevents the word “hosting” from hiding multiple systems.
The useful mental model
The domain is the address, DNS is the set of directions, the website is one destination, and email is another. Protect the address, copy the directions before editing, and test every destination after a change.
Related service:Explore managed websites.
