Skip to content

🐞 Common Mistake&Error

This Page Discuss about common error when configuring EdgeHit-CDN

⚠️ Incomplete Record Chain

During CDN Domain Configuration, CNAME record (Site-Map) is generated that Maps to the traffic Policy Assign to the CDN Domain.

The DNS Records generated are as below: 

<User Domain>.<Domain Prefix>.<System DNS Domain> IN   CNAME <Traffic Policy>
<Traffic Policy>                                  IN   A     <IP Address of CDN Edge Node>

An example would be 

testing.game23.top.EdgeHit DNS-ops.top.      IN   CNAME default.traffic-polcy.EdgeHit DNS4-ops.top.
default.traffic-polcy.EdgeHit DNS4-ops.top.  IN   A     102.140.93.43

Referring to the example above, In order to complete the DNS Query Chain of CDN Domain testing.game23.top., the folowing CNAME Record shall be added. 

testing.game23.top.      IN   CNAME testing.game23.top.EdgeHit DNS-ops.top.


Note that if a site prefix such as .my is configured for the CDN Domain , The site-map value will change to 

testing.game23.top.my.EdgeHit DNS-ops.top.      IN   CNAME default.traffic-polcy.EdgeHit DNS4-ops.top.
so DNS administrator need to configure the value of CNAME to match the name of Site-Map Record.

Info

The DNS Zone of the CDN Domain can be Served by any hosting provider, not necessary needed to be Served by EdgeHit DNS Servers.

Warning

CNAME Record cannot coexist with other records with same name value as stated in RFC 1034 , which is enforced by all DNS Hosting Provider.


⚠️ Missing HTTP(s) Scheme in Cache Purge or Prefetch URL

When performing cache purge or prefetch, the URL must include the full scheme (http:// or https://). Omitting it may cause:

  • Cache operations to fail
  • Requests to be ignored
  • Malformed URL errors

❌ Incorrect : example.com

βœ… Correct : https://example.com


⚠️ Misconception of Geolocational Resource

When going through the documentation, you will notice that in the advanced option field in Server Details of DNS and CDN Server , there are some Geograghical Area Setting. Pic

These settings are at

  • Home > CDN > Server > Details
  • Home > DNS > Server > Details

However, note that these setting are only for reosource tag for logging and management purpose. It will not effect the actual service and request flow.

The Settings thet enable Geolocational based content are Geolocation for DNS Record and Geolocation for Traffic Policy. Which is explained in the Configuration Guide Documentation.


⚠️ Custom origin server host header value not defined

By default, the host HTTP header is set to null by the EdgeHit node when sending requests to the origin server.

This can cause issues in environments such as:

  • Shared hosting, where the origin server relies on the host header to determine which virtual host to serve.
  • Strict security configurations, where the origin server uses the host header for access control or routing logic.

It is Recommended to set the host header to match the CDN domain name (or the expected domain at the origin) to ensure proper routing and compatibility. Only omit or override this value if you're certain the origin server does not depend on it.