Hi,
An old thread.... But I´ve just had the same or at least a similar problem. First reload of the website works, next requests fails with errormessage "no route to host".
In general BarryG ist right, when he says:
BarryG said:No Route to Host is NOT a DNS problem.
But: This problem can result because of dns. In my case it is the website bmsfans.info. This domain name has two ip addresses configured:
> bmwfans.info
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: bmwfans.info
Address: 78.47.130.57
Name: bmwfans.info
Address: 138.201.30.58
If we have two or more dns entries, then usually dns round-robin will be used. In this case, the server 78.47.130.57 is not reachable. So the dns server replies with all the configured ip addresses, each for each after another. So if we get 78.47.130.57 as an answer from the dns server, the request will fail and in this case, the proxy will show the "no route to host" message. But as you can imagine, every possible errormessage could appear, when the utm requests the "faulty" server.
So, if anyone faces this issue, use the sophos´s shell access and use nslookup or an similar tool to check for ip addresses registered to that domain name. After that, check, if both servers are pingable and if services are running (e.g.: telnet xyz.com 80 or telnet xyz.com 443).
Now, we still didn´t solve the problem, we just know the reason. At first you should kindly ask the provider/owner of that website, hopefully he is reachable and willing to fix the problem. But if not, you can temporarily use a workarround in the utm. Simply configure a static host for that specific site and use only the actually working ip address. Looks like that:
And here the result:
Hope that helps.
Best Regards
Sebastian
