DNS A-Record does not get verified

Why This Matters

For JENTIS to function properly, the A record in your DNS settings must point to the correct IP address. If the A record is misconfigured, the tracking JavaScript won’t load, and data collection will fail.

---

How to Check the A Record Setup

1. Use Command Prompt (Windows) or Terminal (Mac/Linux)

Run the following command, replacing the subdomain with your tracking domain (e.g., z832xh.data.anyline.com):

ping your-tracking-subdomain.com 

You should receive a response with an IP address. You can find the correct IP-Address in your DCP. Read more about how to find the correct IP:

If You Don't Get a Response

This likely means the A record is missing, incorrect, or not fully connected. This will prevent the JavaScript from loading, and you may see console errors in the browser.

---

✅ Example Output (Correct Setup)

Pinging z832xh.data.anyline.com [217.160.200.101] with 32 bytes of data: Reply from 217.160.200.101: bytes=32 time=xxms TTL=xxx 

❌ Example Output (Incorrect Setup)

Ping request could not find host z832xh.data.anyline.com. Please check the name and try again. 

---

🔁 Next Steps

• Recheck your DNS settings to ensure the A record points to you dedicated IP.

• After updating, allow time for DNS propagation (can take up to 24 hours).

• Reload the site and verify in the browser console that the JENTIS JavaScript is loading without errors.