View Single Post
Posts: 35 | Thanked: 3 times | Joined on Dec 2011
#8
Originally Posted by reinob View Post
Note that a server bound to 0.0.0.0 as a listening address means that the server accepts connection on any address, normally meaning from any interface (as opposed to, say, only from localhost, only from WAN address, etc.)

So whenever a networking tool wants to show a nice name for 0.0.0.0 (it should not, but it may try) then you get that doubleclick.
Unfortunately I did not grasp this yet. Thank you anyway for your answer!

In my hosts file there are a few additional entries for 0.0.0.0. Doubleclick.net is neither the first nor the last entry. So why does it as the only one out of all appear? Can one rule out that some app or something actually tries to connect to doubleclick.net, but keeps waiting forever exactly due to that hosts file?