1
My question is: what is the difference between DNS and the static resolution method based on /etc/hosts in name resolving during an HTTPS connection? In order to connect to a site using https the first action is ask to DNS for the ip of the requested server (if there are no record in /etc/hosts for that domain).
I'm trying to figure out why I can connect to a server only with the right ip inside /etc/hosts file (and not using DNS).
The URL of the server is "https://www.ovh.it/managerv3/login.pl" and I cannot connect to it if there's not a record "94.23.64.34 www.ovh.it" in /etc/hosts. There's also another fact that I can't explain: when I'm connected to my ADSL I've to use this trick, but when I use tethering through my phone everything works fine (also without changing /etc/hosts).
If I ping the domain www.ovh.it the result is the same on both connections:
PING www.ovh.it (198.27.92.4): 56 data bytes (ADSL)
PING www.ovh.it (198.27.92.4): 56 data bytes (TETHERING)
If I ping the domain ovh.it the result is the same on both connections:
PING ovh.it (94.23.64.34): 56 data bytes (ADSL)
PING ovh.it (94.23.64.34): 56 data bytes (TETHERING)
Using ping (ICMP protocol) the result of the name resolution is the same on both connections. Why using a browser and an HTTPS connection I can't connect to the server with ADSL and there are no problem with TETHERING of my SMATPHONE? And why manually inserting the ip on ovh.it in /etc/hosts it works also connecting with my ADSL?
Additional informations: I tried with Safari, Chrome and Firefox and the result is the same. I tried to reboot laptop and wifi-router (ADSL router). I also tried with a different laptop.