How to Point a Domain to Your Hosting Server
Pointing a domain to your hosting server connects your website address (like example.com) to the server where your website files are stored. This guide walks you through the process, whether you bought the domain and hosting from the same company or from different providers. You’ll need access to your domain registrar’s DNS settings and your hosting provider’s nameserver or IP address information.
What You’ll Need
- Your domain name and access to its DNS management panel (usually at your domain registrar).
- Your hosting account’s nameservers (e.g., ns1.hostingcompany.com) or its IP address (e.g., 192.0.2.1).
- Login credentials for both your domain registrar and hosting control panel.
Step-by-Step
- Find your hosting server’s nameservers or IP address. Log in to your hosting control panel (cPanel, Plesk, or a custom dashboard). Look for a section called “Domain,” “DNS,” or “Server Information.” If you have a shared hosting plan, you’ll typically see two nameservers like
ns1.yourhost.comandns2.yourhost.com. If you have a VPS or dedicated server, you may have a specific IP address instead. - Log in to your domain registrar’s control panel. This is the company where you bought the domain (e.g., GoDaddy, Namecheap, Google Domains, or your hosting company if you bundled). Navigate to “My Domains” or “Domain List” and click on the domain you want to point.
- Locate the DNS or Nameserver settings. Look for a tab or link labeled “DNS,” “Nameservers,” “Domain Management,” or “Advanced Settings.” This is where you’ll change where your domain points.
- Choose the correct update method. There are two common ways:
- Change nameservers (recommended for most hosting): Select “Custom Nameservers” or “Use Custom DNS.” Delete the default nameservers and enter the two nameservers provided by your hosting company. Save the changes.
- Add an A record (for IP addresses): If your hosting gave you an IP address instead, you’ll edit the DNS records. Find the “A Record” or “Host Records” section. Add or edit an A record with host
@(or blank) pointing to your IP address, and another with hostwwwpointing to the same IP. Save.
- Wait for DNS propagation. DNS changes can take anywhere from a few minutes to 48 hours to spread across the internet. Your domain will keep working on the old server during this time, then switch over.
- Verify the domain points correctly. After a few hours (or up to 48), visit your domain in a browser. If you see your website, it’s working. If not, use an online DNS checker tool to see if the nameservers or A records have updated globally.
Common Mistakes
- Using the wrong nameservers: Copying nameservers from an old hosting provider or misspelling them will prevent your domain from resolving.
- Forgetting the www record: If you only set up the root domain (example.com) and not www, visitors typing www.example.com may see an error.
- Changing DNS records instead of nameservers: If your hosting provider gave you nameservers, don’t try to manually add A records unless you’re sure that’s what’s needed. Mixing both can cause conflicts.
- Editing the wrong domain: If you have multiple domains, double-check you’re updating the one you intend to point.
- Not waiting long enough: DNS propagation isn’t instant. Checking too early and assuming failure is a common error.
Tips
- Keep your DNS settings simple: If you’re not comfortable with DNS records, use the nameserver method. It’s the most straightforward and less error-prone.
- Set up email correctly: If you use email with your domain (like you@example.com), make sure your hosting provider’s MX records are correct. If you switch nameservers, the new provider’s default MX records will handle email unless you configure them otherwise.
- Use a DNS checker tool: Tools like whatsmydns.net or dnschecker.org let you see if your changes have propagated worldwide.
- Update your domain’s contact info: Ensure your registrar contact email is current so you receive renewal notices and security alerts.
- Consider using a CDN or proxy: If you plan to use Cloudflare or similar, you’ll point your nameservers to them first, then configure the CDN to connect to your hosting server.
Troubleshooting
Domain not loading after 48 hours: First, check your nameservers or A records with a DNS checker. If they show the correct values, the issue may be with your hosting server (e.g., the site isn’t configured for your domain). Contact your hosting support.
Seeing a “parked” or “default” page: This usually means the domain is pointing correctly, but your hosting account doesn’t have the domain added as a website. Add the domain to your hosting account’s “Addon Domains” or “Domains” section.
Email stops working: If you changed nameservers, your email may now route through the new host. Check your hosting provider’s MX record setup. If you want to keep email with your old provider, you’ll need to manually set the MX records to the old provider’s values.
SSL certificate errors: After pointing, your SSL certificate (if any) may need to be reissued for the new server. Many hosts auto-provision free SSL via Let’s Encrypt, but you may need to trigger it manually.
Domain works for some people but not you: Your local DNS cache may be stale. Clear your browser cache or flush your OS DNS (e.g., ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS).
Frequently Asked Questions
How long does DNS propagation take? Typically 1-48 hours, but most changes are visible within a few hours. The time depends on your ISP and the TTL (time-to-live) set on the old records.
Do I need to change nameservers or just add an A record? If your hosting provider gives you nameservers, change nameservers. If they give you an IP address, use an A record. Some hosts require nameserver changes for shared hosting, while VPS/dedicated often use A records.
Can I point my domain to two different hosting servers? Not for the same domain name. You can use subdomains (e.g., shop.example.com) to point to different servers, but the main domain (example.com) can only point to one server at a time.
Will my website be down during propagation? No. Your domain will continue to resolve to the old server until the new DNS information reaches the visitor’s ISP. There may be a brief period where some visitors see the old site and some see the new one, but it won’t be completely down.
What if I bought my domain and hosting from the same company? Then the domain is likely already pointing to the hosting automatically. You may only need to add the domain to your hosting account if it isn’t already set up.
Do I need to change DNS records for email as well? If you change nameservers, the new host’s default MX records will be used. If your email is with a different provider (like Google Workspace), you’ll need to update the MX records manually to point to that provider.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.