To point a domain to a website, first identify the authoritative DNS provider and follow the destination host’s supported instructions. Check registration, DNS, website mapping and HTTPS as separate parts of the connection.
You bought a domain at one company and hosting at another. Now you need to connect them so visitors typing your domain land on your website. This process — “pointing” your domain — sounds technical, but its timing depends on the providers, current records and cached answers.

The Domain Name System (DNS) is the internet’s phone book: it translates your domain into the IP address of your server. You can connect a domain to hosting in two ways:
Method 1 — Change nameservers.
Nameservers decide who manages your domain’s DNS records. When you switch to your host’s nameservers (for example, ns1.yourhost.com and ns2.yourhost.com), the delegated provider publishes DNS; verify and preserve all required records instead of assuming they are created automatically.
Method 2 — Update A records (and CNAME).
You keep DNS at your registrar (or a service like Cloudflare) and just point specific records at your host’s IP address.
Before switching, note any existing DNS records (especially MX records for email). If your email is hosted elsewhere — for example, with Google Workspace or Microsoft 365 — you’ll need to recreate those records at your host.
@ (the root domain) and set its value to your server IP.www by either:www with the same IP, orwww pointing to your root domain.Tip: lowering the record’s TTL (time to live) a day before a planned change can support planning, but does not shorten copies already cached under the previous TTL.
DNS changes aren’t instant. Servers worldwide cache old records until their TTL expires. Timing varies by the existing cached answers, delegation and provider behaviour; do not treat a fixed interval as a worldwide guarantee.
To check progress:
nslookup yourdomain.com or dig yourdomain.com from a terminal.Once your domain loads the hosting’s default page or your site, install SSL so it works on HTTPS — see What Is SSL?.
“This site can’t be reached” / DNS_PROBE_FINISHED_NXDOMAIN
The domain isn’t resolving yet. Wait for propagation, check nameservers are spelled correctly, and confirm the domain isn’t expired.
Site loads the old website
Your device or ISP is using cached DNS. Clear cache, try another network, or wait for the TTL to expire.
Email stopped working
Review current authoritative mail records and the receiving service before assigning a cause. Re-add the MX, SPF, and DKIM records for your email provider. Our SPF, DKIM, and DMARC guide explains each.
www works but root domain doesn’t (or vice versa)
Review both names’ records, server mapping, HTTPS and intended redirects. Make sure both @ and www point to your server.
SSL error after pointing
Use the host’s supported validation process and inspect the actual certificate and hostname mapping. Some preparation may be possible before the public web change.
Registrar lock or pending transfer
An ordinary registrar-transfer lock is different from DNS-edit permissions. Check the actual status and provider policy.
Which method should I use?
Beginners: change nameservers. If you use Cloudflare or keep email and other services elsewhere, use A records.
Does pointing a domain transfer it to my host?
No. Pointing only changes where the domain directs visitors. The domain stays registered where it is. To move registration, see how to transfer a domain.
Record the domain registrar, authoritative DNS provider and website host. They may be the same company or three different companies. The registrar controls the registration relationship, authoritative DNS publishes the relevant records, and the website host serves the application.
You can point a domain to a different website environment without necessarily transferring its registration. ICANN’s registrant transfer FAQ distinguishes changing hosting or nameservers from moving registration. Follow the actual provider instructions rather than treating every change as a transfer.
Use our nameservers versus DNS records guide to understand the distinction. Editing a record in a dashboard that is not authoritative may leave the public answer unchanged. Locate the active control point before making a production edit.
Write the exact names that should reach the website, including the root domain, www and any required subdomains. These are separate DNS names even when the intended user experience is the same. Check the destination’s supported domain-verification process.
When you point a domain, decide which public address the application will use and how the alternative is handled. DNS routing and an HTTP redirect are different mechanisms. A CNAME does not by itself configure the application’s preferred public URL or create a browser redirect.
Use the records or nameservers supplied for the purchased website service. Some products request an IP address, some a hostname and some an account-verification record. Do not substitute the server information from another customer’s tutorial.
Cloudflare’s zone-apex documentation explains that the appropriate record depends on the hosting service. Its supported apex behaviour should not be assumed to apply to every DNS provider. To point a domain correctly, follow the capabilities of the provider that publishes your zone.
Inventory mail routing, authentication, service verification and important subdomains before changing delegation. A DNS import or scan may not reproduce every record. Compare the required zone with the destination rather than relying solely on an automatic completion message.
Use the DNS record types guide to classify the entries. To point a domain for web traffic, you should not needlessly change an unrelated mail service. Identify the exact scope and keep a record of the former values.
Confirm that the destination accepts the hostname and serves the intended site. Check the provider’s domain binding, document root or application mapping as applicable. DNS can direct a request to a server that still does not know which website to show.
Prepare HTTPS through the host’s supported certificate-validation process and test what is possible before cutover. Do not promise that all certificates require the same sequence. When you point a domain, DNS resolution, server mapping and certificate coverage need separate checks.
Review the current TTL and allow for answers already cached under earlier values. Lowering a TTL does not retroactively shorten every copy in use. Record the previous configuration and the planned change time.
Our TTL guide and DNS propagation guide explain why different observations can coexist. To point a domain safely, plan acceptance and recovery around the actual dependencies rather than a guaranteed worldwide completion time.
Check the relevant record type and hostname, then test the public website workflow. Record the resolver or authoritative server queried and the observed answer. A public checker samples particular locations; it is not a complete census of every cache.
Use dig and nslookup to collect focused evidence. After you point a domain, a correct DNS answer still needs a separate browser check for HTTPS, redirects, site content and important functions.
Record the change, former values, responsible owner and conditions for rollback. Keep the source service available through the agreed verification period when a website is moving. Review changing application data separately from DNS settings.
When you point a domain, assign an owner to each untested item. A homepage displaying correctly does not prove that forms, mail or checkout work. Close the change only after the required checks and remaining limitations are documented.
| Layer | Question | Evidence |
|---|---|---|
| Registration | Who controls the domain account? | Authorised owner and recovery route |
| Authoritative DNS | Where are public records published? | Current delegation and intended zone |
| Website destination | Does the service accept the hostname? | Provider instructions and site mapping |
| HTTPS | Does the certificate cover the name? | Supported validation and browser result |
| Other services | Which records must remain? | Mail and verification inventory |
| Acceptance | Which public functions were tested? | Passed, failed and untested checks |
Complete the worksheet before you point a domain, especially when several people or suppliers administer different layers. Keep credentials in the approved credential system rather than copying them into a general change note.
Check which address the tested client resolves and which application responds. An old DNS answer, browser content cache, CDN cache or destination mapping can produce different symptoms. Preserve the actual observation before clearing several unrelated caches.
If the answer differs from the intended authoritative value, investigate that route. If the answer is correct but the old content remains, inspect the application and cache layers. To point a domain successfully, you need to locate the failing layer rather than repeat the same DNS edit.
Compare the root and www configuration separately, including server acceptance and certificate coverage. Confirm the intended redirect. Do not add conflicting records merely because both names should eventually show the same website.
A provider-specific apex feature may differ from ordinary record behaviour. Use the relevant documentation and preserve unrelated records. After you point a domain, test the exact public hostname that the site’s links and campaigns use.
Review whether mail routing and authentication records remain correct at the authoritative provider. Also verify that the receiving service and accounts still exist. A website resolving correctly is not evidence that incoming and outgoing mail are healthy.
Our DNS and email troubleshooting guide separates routing, submission and recipient handling. Do not assume every mail failure is caused by MX records merely because it followed a website change.
Check the current provider instructions and the actual validation evidence with the responsible administrator. A nameserver change can require coordinated DNSSEC handling. Do not remove security settings blindly to make one lookup succeed.
Review the DNSSEC guide for the service boundary. To point a domain during a provider change, keep the registration, delegation and validation steps coordinated through the supported process.
Consider a hypothetical business that keeps employee mail with its existing mail provider while moving the website. The maintainer first records authoritative DNS and the mail-related entries. The new website service supplies the required destination records and domain-binding steps.
The team prepares and tests the destination through a permitted route, then updates only the agreed web configuration. It checks the root and www experience, relevant application functions and controlled mail sending and receiving. The change record keeps any unresolved issue with its owner.
This example shows how to point a domain with an understood scope. It is not a change Hostreta performed, a guarantee of uninterrupted service or a measured propagation result. Adapt the plan to the actual providers and application.
Promotional recommendation: Consider KAWEDMA’s domain and hosting services if you need a service for the website or help understanding its supported connection process. Confirm the specific product, domain-management controls and support responsibilities. Registration and hosting can remain separate when that arrangement fits your needs.
Affiliate disclosure: Hostreta may earn a commission if you purchase through this link. hosting.com’s shared web hosting plans are another option to assess. The current destination page lists shared hosting; confirm the plan and domain-connection instructions. This is not an independent performance test or a claim that a purchase automatically completes DNS configuration.
Before you point a domain to either service, use the same requirements and verification steps. A referral relationship does not replace control of the domain, the correct records or a tested public website.
Not necessarily. Review the registrar and provider’s supported configuration. Registration transfer, delegation and individual record edits are different operations with different scopes.
No. The destination still needs the application and the correct hostname mapping. DNS routing alone does not copy files, import a database or create a mailbox.
No. Transfer restrictions and the ability to edit DNS are separate matters. Check the actual domain status and provider policy rather than assuming that an ordinary registrar-transfer lock prevents all record changes.
The required public names reach the intended application, HTTPS and redirects work, related services have been checked and the change record identifies any remaining limitations. To point a domain is to connect a service deliberately, not simply to save a record in a dashboard.
When you point a domain for a client or colleague, provide a short record of the authoritative DNS provider, intended web host, changed records and completed tests. Identify the person responsible for renewal and future changes. Keep access credentials outside the ordinary handover note.
Record which related services were checked and which remain untested. If mail is managed elsewhere, name that service rather than implying the website host operates every function on the domain. Include the supported recovery route and the previous configuration where appropriate.
Review the record after another provider change or a significant application move. To point a domain is a small part of operating the website; the ownership and verification record makes the next change easier to assess.
We may earn a commission on purchases made through these links, at no extra cost to you.
Don’t miss the chance to participate in the biggest giveaway of this year.