This might be a stupid question, and I am sure it has already been answered, but I haven't found the answer in a day and a half.
When I ping a valid DNS name on my home network (ex: "m6809", a laptop on my network, sitting right next to me, up and running) it resolves to an OpenDNS server. This is what I get:
C:\Users\Sean>ping m6809
Pinging m6809.lanfest [208.69.36.132] with 32 bytes of data: Reply from 208.69.36.132: bytes=32 time=15ms TTL=52 Reply from 208.69.36.132: bytes=32 time=11ms TTL=52
Ping statistics for 208.69.36.132: Packets: Sent = 2, Received = 2, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 15ms, Average = 13ms Control-C ^C C:\Users\Sean>
The name is resolving to an OpenDNS server, not the IP of the laptop. I can ping the computer with the IP address with no problem, it's at 192.168.1.20, and if I add it to my hosts file I have no problem. If I remove the OpenDNS entries, or let my ISP to override the DNS server settings, it works with the name. However, I don't want to edit my host file every time I add a device to my network and I still want to use OpenDNS.
I have the two OpenDNS server IPs in the DNS Forwarder, and it is enabled. I also have the servers entered into the General Setup screen, with "Allow DNS server list to be overridden by DHCP/PPP on WAN" unchecked.
Until the HDD in my Monowall decided to crap the bed two days ago I didn't have the problem. Perhaps, this is not an Monowall issue, but I would be interested what kind of advice people have here. I don't know what else to add info-wise, but ask and I will post it. Thanks!
|