How can I check that my domain points to the correct hosting?

Procédure

This guide helps you check whether a domain or subdomain is correctly directing visitors to the expected hosting. It is especially useful if your site does not display, shows an older version, or has just been moved to a new server.

The check uses Google Admin Toolbox Dig. This external tool displays the DNS information publicly visible for your domain, without requiring any command or special software.

Before you begin

You need to know the IP address your domain should point to.

For an LWS hosting or server, see the guide Retrieve the IP addresses of my LWS services to find the value corresponding to your plan.

If your domain must be linked to an external service, use only the IP address or destination name provided by that service.

Check the main domain

1. Open the Google Admin Toolbox Dig.

2. In the Name field, enter your domain name without https://, without www and without adding a page.
   
   

   Example:

   CodeCopy

   example.com

3. Select the A record type.

   An A record indicates the IPv4 address to which the domain points.

4. The search starts automatically
5. In the result, look for the line of type A. The IP address shown in the response corresponds to the destination currently visible from Google.
   
6. Compare this address with the expected IP address of your hosting:
   • if the two addresses are identical, the main domain points to the correct hosting;
   • if the addresses are different, the domain currently points to another server;
   • if no address is displayed, no A record is publicly visible for this name.

Check the www address

The domain example.com and the address www.example.com are two distinct names. They must therefore be checked separately.

1. In Google Admin Toolbox Dig, replace the searched name with:

   CodeCopy

   www.example.com

2. Select the CNAME type, then start the search.
3. If a destination is displayed, check that it corresponds to:
   • the main domain, for example example.com;
   • or the name provided by your hosting or external service.
4. If no CNAME is displayed, perform a new search by selecting the A type.
5. Then compare the IP address obtained with that of your hosting.

It is normal for www to use a CNAME pointing to the main domain instead of containing an IP address directly. In this case, www will follow the main domain’s pointing.

Check which DNS servers manage the domain

This check is useful if Google Dig shows an old IP address or a value different from the one recorded in your LWS customer area.

1. Enter the main domain again, without www.
2. Select the NS type.
3. Start the search.
4. Check the server names displayed in the result.

The NS records indicate which DNS servers currently manage the domain’s DNS zone.

If the servers displayed belong to another provider, the DNS zone visible in your LWS customer area may not be the one used on the Internet. The change must then be made from the service that actually manages those DNS servers.

Take DNS propagation into account

After a DNS change, the new value may appear quickly in Google Dig, while some networks are still using the old value stored in their cache.

Check that everything works

When the DNS results match the expected destination:

1. Open your site with the main domain:

   CodeCopy

   https://example.com

2. Also test the address with www:

   CodeCopy

   https://www.example.com

3. Check that both addresses open the correct site.
4. If an older version appears, repeat the test in a private browsing window.

Common issues

Google Dig still shows the old IP address

Check the NS records to make sure you modified the DNS zone actually used by the domain.

If the correct zone was modified recently, wait for propagation. There is no need to delete and recreate the record several times.

The main domain works, but not the www address

Search separately for www.yourdomain.com in Google Dig.

If no A or CNAME record is returned, or if the destination is incorrect, check the www record in the active DNS zone of the domain.

Google Dig shows the correct address, but the site does not open

The DNS pointing may be correct while the problem comes from the hosting.

In particular, check that:

• the domain has been added to or associated with the hosting;
• the site is in the correct folder;
• the hosting is active;
• the SSL certificate is installed for the domain concerned;
• the site is not experiencing a technical error.

An older version of the site still appears

Test the site in a private browsing window, then clear the browser cache if necessary.

If your site uses a cache system, a CDN, or a WordPress cache plugin, it may also keep an older version of the pages.

The IP address displayed is not the server’s, but the site works

Your domain may use a proxy or a CDN, such as Cloudflare. In this case, the publicly visible IP address may belong to the proxy and not directly to your hosting.

Do not modify the DNS zone based solely on this difference. Check the configuration from the service that manages the proxy.

The site works differently depending on the device

Perform an AAAA type search in Google Dig.

An AAAA record points the domain to an IPv6 address. If it contains an old destination, devices using IPv6 may reach a different server than those using the A record.

Only delete or modify this record if you know the expected IPv6 address or if your provider confirms that it should not be used.