ping hda resolves to an address outside my network?
Posted: Wed Apr 04, 2012 7:30 pm
Greetings,
I have Amahi ujp and running with one small glitch. home.com, hda, calendar.home.com etc all resolve to an internet address external to my domain.
I have dhcp *disabled* on my amahi server for one specific reason: I want to allow my wireless router to do time, web site and key word web filtering by mac address. this seems to work if the router is the source of dhcp addresses.
so, dns and all other services reside on amahi and are configured. dns is configured for opendns.com. the wireless router has dns entries pointing to opendns.com.
NOTE: wireless router is configured with a hardcoded ip address given by my ISP. this is the address of my network which appears on opendns.com in my registration there. wireless router DNS entries point to openDNS nameservers - 208.67.222.222 and 208.67.220.220
everything comes up. clients get dhcp addresses from the wireless router. domain suffix seems all rosie at the client side. clients have a gateway address of 192.168.1.1 which is the address of the wireless router/dhcp server.
the problem is ... name resolution of local names "hda", home.com, calendar.home.com all resolve to a single, external ip address 67.215.65.132. when you tracert from a win client to hda it goes from 192.168.1.1 -> 67.215.65.132 and then starts bopping all over the internet...
67.215.65.132 is an opendns server (hit-nxdomain.opendns.com [67.215.65.132])
suggestions?
Any idea where I've gone wrong in my config? Will it simply not work
I have Amahi ujp and running with one small glitch. home.com, hda, calendar.home.com etc all resolve to an internet address external to my domain.
I have dhcp *disabled* on my amahi server for one specific reason: I want to allow my wireless router to do time, web site and key word web filtering by mac address. this seems to work if the router is the source of dhcp addresses.
so, dns and all other services reside on amahi and are configured. dns is configured for opendns.com. the wireless router has dns entries pointing to opendns.com.
NOTE: wireless router is configured with a hardcoded ip address given by my ISP. this is the address of my network which appears on opendns.com in my registration there. wireless router DNS entries point to openDNS nameservers - 208.67.222.222 and 208.67.220.220
everything comes up. clients get dhcp addresses from the wireless router. domain suffix seems all rosie at the client side. clients have a gateway address of 192.168.1.1 which is the address of the wireless router/dhcp server.
the problem is ... name resolution of local names "hda", home.com, calendar.home.com all resolve to a single, external ip address 67.215.65.132. when you tracert from a win client to hda it goes from 192.168.1.1 -> 67.215.65.132 and then starts bopping all over the internet...
67.215.65.132 is an opendns server (hit-nxdomain.opendns.com [67.215.65.132])
suggestions?
Any idea where I've gone wrong in my config? Will it simply not work