http://support.microsoft.com/kb/139270/EN-US/
If the OpenDNS updater altered the appropriate registry keys to prefer NetBIOS over DNS, it would eliminate many common problems with local names being resolved as NXDOMAIN.
6 Comments
If the OpenDNS updater altered the appropriate registry keys to prefer NetBIOS over DNS, it would eliminate many common problems with local names being resolved as NXDOMAIN.
6 Comments
Who voted for this idea
Comments
written by rotblitz 993 days ago - show/hide this comment
Rating: -1
| Rate Comment:
+
-
The only issue with that article is that it is for dead OS's only. IE nothing before Windows NT 4.0. A quote from the article including any spelling errors.
"Note By default, Windows 2000 and later versionss try to resolve a name through DNS before they try to resolve it through the earlier-version node-type configuration. DNS or NetBIOS lookup order priority cannot be modified by applying this registry entry in operating systems that are later than Windows NT 4.0."
I also found they have already come up with a way to deal with this issue. You need to have the OpenDNS updater installed & have typo correction enabled. You setup the software to the user for your account & it will add the computers that it sees on your network. Because they are added to the "Exceptions for VPN users" thus dealing with your issue.
If you want a more elaborate method I could setup a PFSense box for you that would not require installing software onto a computer in your network.
Local DNS should always have presidence. The default entry for localhost then gifts the O.P. behavior and still allows MVPS.com solution to work too
| Edit
if you set up dns properly on your network this wouldnt be a issue, allow your router to cache the dns requests instead of directly giving clients opendns server ips
I fully suggest this idea as well. I've had to go in and manually add VPN exceptions for specific computers in certain situations. It's not always with old machines either.
Sign in to comment or register here.





