Private/Local Network Addresses Appearing in OpenDNS Log
I am seeing private/local network addresses appearing in my OpenDNS log of domain look-up requests. Entries -- with hundreds of hits each -- include "family.home," "[nameofchild]-pc.home," "hp0ad494.home," "wpad.home," "isatap.home," etc.
I'm very much computer literate but not very knowledgeable about network operations. Is this normal? It seems strange. Why would transmitting local network information to OpenDNS be needed or necessary? If not normal, how might I prevent my local/private network locations from being transmitted over the internet to OpenDNS?
Thanks in advance for any assistance.
-
If you have configured the OpenDNS resolver addresses on the LAN side (of the router, or on end user devices), then you send out also your internal name resolution attempts to OpenDNS. That said, under these circumstances this is totally normal.
"how might I prevent my local/private network locations from being transmitted over the internet to OpenDNS?"
You configure the OpenDNS resolver addresses only on the WAN side of your router if you can. Or you operate an own internal DNS server with the OpenDNS resolver addresses as forwarders.
-
"I am unable to access the link above... Is there another way to access it?"
No, this is normal. (Maybe OpenDNS staff may still see it though.) This outdated article would have no relevance anymore since OpenDNS gave up the NXDOMAIN redirection, making VPN exceptions configuration obsolete. The rest of what I said back in February is still valid.
What is your problem, and what additional information did you expect from this article?
Please sign in to leave a comment.
Comments
6 comments