Host Forgery in real-time events

If you using Artica in transparent mode you have probably seen this Host Forgery (NONE_NONE:409) error and your browsers shows the SSL_ERROR_RX_RECORD_TOO_LONG error in browsers

Red requests meand clients cannot access to the remote web server, this issue is important to fix it.

This error is due to the fact that there is a difference in the hostname resolution between the browser and the proxy.

The browser resolves the domain with an IP A but the proxy resolves the same domain with an IP B.

First behavior - DNS switching

This error can occur if both the proxy and the client use the public DNS directly and some websites use the round-robin method.

Randomly, the DNS server responds with different IP addresses.

Second behavior - desynchronized DNS or DNS cache.

If the clients do not use the same DNS server, it is possible that one of them has cached an IP address for the domain while the other uses refreshed records.

As a result, the proxy does not resolve the same IP as the clients.

In both cases the solution is:

1. Use a DNS server in your network and don't use your ISP's DNS (Artica allows you to do this with the DNS Cache service).
2. Make sure that clients and the proxy share the same DNS database or the same local DNS servers.