Configuring DNS settings for an externally hosted domain requires pointing your domain registrar’s nameservers to your hosting provider or managing records directly if you use a separate DNS service. This process ensures that when users type your address, they are routed to the correct server. Proper configuration involves updating A records for web traffic and MX records for email, ensuring global accessibility and reliability for your online presence.
Understanding Nameserver Delegation
The first step in connecting a domain purchased from one provider (like GoDaddy, Namecheap, or Cloudflare) to a website hosted elsewhere is changing the nameservers. Nameservers act as the phonebook of the internet, translating human-readable domain names into IP addresses. When you purchase a domain, it typically defaults to the registrar’s basic nameservers. To host a website on an external platform, such as Bluehost, SiteGround, or AWS, you must delegate authority for your domain to the hosting provider’s DNS infrastructure.
Log in to your domain registrar’s control panel. Navigate to the DNS Management or Nameserver Settings section for your specific domain. You will usually see options to either manage records manually or use custom nameservers. Select the option to use custom nameservers. Enter the nameservers provided by your web host. These often look like
ns1.hostingprovider.com and
ns2.hostingprovider.com. Save the changes. Note that propagation can take anywhere from a few minutes to 48 hours, though it is often much faster today. If you need to register multiple domains pointing to the same infrastructure, refer to our guide on
Is it possible to register 2 domains for the same IP? to understand how shared hosting environments handle multiple distinct domains.
Essential DNS Records for Web Hosting
Once nameservers are pointed correctly, or if you choose to manage DNS records at the registrar level instead of delegating entirely, you must ensure the critical records are present. The most important record is the A record. An A record maps your domain name directly to an IPv4 address. For example, if your web server has the IP address
192.0.2.1, you create an A record with the host
@ (representing the root domain) and the value
192.0.2.1. This tells browsers exactly where to find your website files.
For subdomains, such as
www or
blog, you can either create separate A records or use CNAME records. A CNAME record aliases one name to another. It is common practice to set the
www subdomain as a CNAME pointing to the root domain (
@). This simplifies maintenance because if you change the main IP address, the
www subdomain updates automatically. However, some providers prefer A records for all subdomains for performance reasons. Always verify the specific requirements of your hosting provider, as some may require explicit A records for both root and www.
Email Configuration and MX Records
Web traffic is not the only thing relying on DNS; email delivery is equally dependent on correct record setup. If you plan to send emails from your domain, you must configure MX (Mail Exchange) records. These records tell other mail servers where to deliver messages addressed to your domain. Unlike A records which point to servers, MX records point to mail servers and include a priority number. Lower numbers indicate higher priority.
Enter the MX records provided by your email host. For instance, if using Google Workspace, you might see entries like
ASPMX.L.GOOGLE.COM with priority
1. If using Microsoft 365, you will have different hostnames and priorities. Ensure that no conflicting MX records exist from previous setups, as this can cause emails to bounce or arrive in the wrong inbox. For more details on email routing issues, see
How can an email addressed to somebody else arrive in my inbox?. Additionally, SPF (Sender Policy Framework) TXT records should be added to prevent your emails from being marked as spam by recipient servers.
Troubleshooting Propagation Issues
After making changes, it is crucial to verify that they have propagated globally. Use tools like
dig or online DNS checkers to query your domain from various locations. Run the command
dig yourdomain.com A in your terminal. The output should show the IP address you configured. If you receive a timeout or an old IP, the changes may still be propagating. Clear your local DNS cache if you are testing on your own machine. On Windows, use
ipconfig /flushdns; on macOS, use
dscacheutil -flushcache.
If the records appear correct but your website does not load, check for typos in the IP address or nameserver entries. Ensure that your firewall allows incoming traffic on ports 80 and 443 for HTTP and HTTPS. Sometimes, SSL certificates fail to install because the DNS is not fully resolved. In such cases, wait for full propagation before retrying certificate issuance. If you suspect a misconfiguration affecting network performance after recent changes, consult
Troubleshooting Slow Network After Promoting Secondary Domain Controller and Deleting Old Primary Domain Controller for broader network diagnostics, although this is less likely related to standard web DNS.
Frequently Asked Questions
Can I use my registrar's DNS for an external host?
Yes, you can manage all DNS records at your registrar while hosting your site elsewhere. You simply add A and CNAME records pointing to your host's IP or hostname without changing nameservers. This gives you centralized control over all your domains regardless of where they are hosted.
Why do I get a "Server Not Found" error after changing DNS?
This usually indicates that the A record is missing or points to an incorrect IP address. Verify that the host field is set to
@ for the root domain and that the IP matches your hosting provider's instructions. Also, allow time for propagation before assuming the configuration is broken.
Do I need to update DNS if I change web hosts?
Yes, you must update your DNS records or nameservers to reflect the new hosting environment. If you keep old records, visitors will still be directed to the previous server. Coordinate with your new host to get the exact IPs and records needed before making changes.
What happens if I mix A records and CNAMEs incorrectly?
Mixing them improperly can cause resolution failures or loops. For example, you cannot have a CNAME and an A record for the same host name simultaneously. Most DNS providers will reject such configurations. Stick to A records for the root domain and CNAMEs for subdomains unless your provider specifies otherwise.
How long does DNS propagation actually take?
While technically up to 48 hours, modern DNS propagation often completes within 15 minutes to a few hours. Factors like TTL (Time to Live) values set previously affect speed. Lower TTLs before making changes can speed up the process significantly.