Pinging computer name in LAN results in public IP?
- by Bob
Hi,
I recently introduced a new machine to my LAN. The computer name for this machine is 'server'. Historically I've been able to access machines from my home network (from a web browser or RDP) using the machine name and it resolves to a local IP address just fine. However, I can't seem to do this anymore.
When I ping the computer name, I get the following:
C:\Users\Robert>ping server
Pinging server.router [67.215.65.132] with 32 bytes of data:
Reply from 67.215.65.132: bytes=32 time=24ms TTL=54
Reply from 67.215.65.132: bytes=32 time=23ms TTL=54
Reply from 67.215.65.132: bytes=32 time=24ms TTL=54
Reply from 67.215.65.132: bytes=32 time=24ms TTL=54
I notice also that it appends the 'router' suffix to my domain name for some reason. 'router' is the name of my router, obviously. I'm also using OpenDNS as my DNS provider (configured through my router so it gets passed down through DHCP).
Why is this not working for me? Can someone explain how the DNS resolution should take place? For LAN resolution, it shouldn't go straight to OpenDNS. I thought that each Windows machine kept it's own sort of "mini DNS server" that knows about all machines on the local network and it first tries to resolve using that.
Please let me know what I can do to get this working!
