nslookup and tracert inconsistencies – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.
But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about windows, networking, windows-7, virtual-machines, virtualbox.
In a Windows 7 VirtualBox guest with NAT and an OpenVPN connection issued by the host,
tracert behave differently w.r.t. name resolution:
nslookup hostnameworks, using
10.0.2.3as DNS server
tracert hostnamecannot resolve hostname
tracert fqdncannot resolve fqdn
tracert ip-addressworks and shows host name, routing via
traceroute hostnameworks in the host, routing directly via
The host I am trying to reach is within the network where I dial in using OpenVPN. Name resolution works well for globally reachable hosts.
What could be the reason? How can I find out? I already tried disabling IPv6 for the network connection, and disabling firewall on both host and guest, and changing network type to “Bridged” in VirtualBox.
I have the following setup:
- Ubuntu 13.04 x64 host
- Intel PRO/1000 virtual network adapter attached to NAT
- Windows 7 x86 guest, fully patched
- OpenVPN connection issued by the host
- Same host name in Windows 7 guest and Ubuntu 13.04 host
Found a solution in this answer on SO:
[Put] a single entry reading “.” in the “Append these DNS suffixes (in order)” in the “Advanced TCP/IP settings” dialog.
tracert and friends by default tries some non-DNS protocol first, which fails in my setup.