#1. Yes, I configured this connection directly (not on ZS) and tried the link is accessible from same connection. In ZS>DNS>OPTIONS> 184.108.40.206 AND 220.127.116.11 ARE SET. Is that right one for DNS??
On Linux I tried traceroute and the below two lines are the result-
1 192.168.0.75 (192.168.0.75) 0.181 ms 0.112 ms 0.106 ms
2 192.168.0.75 (192.168.0.75) 2621.616 ms !H 2621.590 ms !H 2621.560 ms !H
On windows the tracert shows the result –
1 <1 ms <1 ms <1 ms 192.168.0.75
2 192.168.0.75 reports: Destination host unreachable.
#2. When I ping this site without using www from ZS the result is -> From 192.168.0.75 icmp_seq=6 Destination Host Unreachable. And once I tried ping with http://www.site name and the result is ->
64 bytes from hit-nxdomain.opendns.com (18.104.22.168): icmp_seq=72 ttl=51 time=378 ms
So you want to use OpenDNS, looks like your configuration for ZS DNS is correct.
Is the address you are trying to reach 192.168.0.75? This address belongs to a local block of addresses, it’s not routable and can only be used on the LAN. I am not sure why you want to access that IP address, as it seems that in reality you want to use hit-nxdomain.opendns.com
This is what I can see:
22.214.171.124 is the external IP that you should use if you need to access host hit-nxdomain.opendns.com by IP address.
Try to ping it and it most likely is going to work.
A new thing I have observed. We have three interfaces and one of them has static IP so I added static IP to the relative ETH. This site is not accessible after adding the static IP and when I remove the IP, it is. I checked with balancing rules also but this issue persists. So suggest for this one now.