DNS and Subdomain Configuration Errors: Solutions and Guidance

If you encounter an error while validating your TAGGRS subdomain (DNS Error), or if you navigate to your subdomain and receive an error, this guide provides insights into common issues and their resolutions.

DNS and Subdomain Configuration Errors Solutions and Guidance

First things first

Haven't added DNS records to your hosting yet, preventing you from configuring your subdomain? Check out our page on how to configure a subdomain on TAGGRS.

Common DNS Errors and Their Solutions:

Initial Checks:

Ensure your DNS settings are correctly configured. Use tools like MX Toolbox to check your records:

  • IP Address (A type): It should match the one shown in the TAGGRS Dashboard.
  • IPV6 Address (AAAA type): This should typically be empty. If records are present, they should be removed via your hosting provider. This varies by hosting. Therefore, you will need to contact your hosting provider.


Checked? Then check the rest of the possible errors. 

Duplicate Subdomain Records

  • Issue: A duplicate subdomain is detected (e.g., //sst.taggrs.io.taggrs.io instead of //sst.taggrs.io/).
  • Solution: Review your DNS configuration for any duplicates and ensure the subdomain is correctly set without URL repetitions.

No DNS Records Found

  • Issue: No DNS records exist for the subdomain; the container lacks a DNS record.
  • Solution: Add an A record or CNAME record in the DNS management panel that points to the correct IP address or hostname. Subdomain not yet configured? Check out our guide on how to configure a subdomain.


Invalid DNS Record

  • Issue: The DNS record is an AAAA record and URL validation fails, or a CAA record is present that may block SSL certification.
  • Solution: Confirm that the DNS type (A, AAAA, CNAME, etc.) and its value align with the requirements of the hosted services. Utilize tools like MX Toolbox to inspect AAAA and CAA records. Ensure CAA records include 'letsencrypt.org' to facilitate SSL certification requests. If the CAA record does not mention 'letsencrypt.org', it may need modification to allow SSL requests by TAGGRS.

No A Record Found

  • Issue: No A record exists for the subdomain; the container's IP address is missing.
  • Solution: Establish an A record that points to the correct IP address where the container is hosted.


Subdomain Errors

This is what your subdomain should look like. 


500 Error

If you get a 500 error on your subomdain you should contact TAGGRS support.


502 Errors: Load Balancer Issues

Check status.taggrs.io for any server issues. If none are listed, contact TAGGRS support to investigate load balancer configurations.


503 Errors: Server Availability

Confirm server status on status.taggrs.io. If servers are operational but the issue persists, contact support.

503-error (1)


DNS validation or propagation may not be complete. Recheck DNS settings and allow up to 24 hours for changes to propagate. Validate DNS within TAGGRS settings if necessary.

504 Error

If you get a 504 error on your subomdain you should contact TAGGRS support.


403 Error

Ensure your web container is published in Google Tag Manager. Also ensure instead of using the GTM ID from your server container, utilize the Measurement ID from Google Analytics 4 (GA4).


404 Error

A 404 error can occur for various reasons:

- SGTM Container Removed: If the SGTM container for your site has been removed.

- SGTM Container Not Published: If the SGTM container is not published.

- Incorrect Configuration Code: When using the wrong configuration code.

Other solution: Within the container settings, your current domain is listed. Here, the subdomain of TAGGRS should be specified; otherwise, you may encounter a 404 error.

404 error

SSL Error on the Subdomain (Connection is not private)

If a developer accidentally changes something in the DNS settings, you might get an SSL error on the subdomain. This look like this:

SSL Error on the Subdomain (Connection is not private)

This error only causes a complete loss of data if you've also installed the enhanced tracking script. In this case, ask the developer to check if the DNS settings of your container still match the current settings.

You can also check it yourself by going to mx toolbox, then selecting DNS Lookup, entering your subdomain, and you will see the DNS settings of your subdomain. Make sure the IP Address (A type) matches the one in the TAGGRS Dashboard. The IPV6 Address (AAAA type) should be empty. If this is not the case as in the example below, you will need to remove them within your hosting. This varies by hosting. Therefore, you will need to contact your hosting provider.


File Not Found

If you get a File not found. error on your subomdain you should contact TAGGRS support.


Wrapping up

This guide has provided detailed solutions for addressing DNS and subdomain configuration errors within your TAGGRS setup. If your issue persists or if you encounter a different problem that might be relevant to other users, please reach out to us through a support ticket.