Re: [Dnsmasq-discuss] resolving short names
On Mon, May 30, 2011 at 10:54 AM, Rance Hall ran...@gmail.com wrote: I have a small home network with several nodes, some static ips, others from dnsmasq's dhcp server. all have same netmask and class. Three of the nodes( two servers, one client) are Windows Active Directory domain members using the windows dns service for a different domain name. Most of the clients on the dnsmasq side are able to resolve short names just fine. I need to know if there is a way to configure dnsmasq to look at the Windows AD DNS to resolve short names it doesn't understand. despite the fact that I have domain needed set in the dnsmasq.conf to keep dnsmasq from actually forwarding incomplete names. Ive already got a server= line in my dnsmasq.conf which fixed full name resolution just fine. here is what I want to happen: dnsmasq gets request to resolve short name like andromeda (name of one of my windows servers) dnsmasq tries to find andromeda in either /etc/hosts or the dhcp leases and fails. dnsmasq can't forward to upstream servers an incomplete name, so it assumes that the windows service is handling that name, and checks. Is it infeasible to add the domain name to the domain search order in the client configuration? All OSes I've seen are capable of searching multiple suffixes automatically. If windows can find a listing for andromeda fine, return it. If not, then fail. Possible? Thanks. ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
[Dnsmasq-discuss] resolving short names
I have a small home network with several nodes, some static ips, others from dnsmasq's dhcp server. all have same netmask and class. Three of the nodes( two servers, one client) are Windows Active Directory domain members using the windows dns service for a different domain name. Most of the clients on the dnsmasq side are able to resolve short names just fine. I need to know if there is a way to configure dnsmasq to look at the Windows AD DNS to resolve short names it doesn't understand. despite the fact that I have domain needed set in the dnsmasq.conf to keep dnsmasq from actually forwarding incomplete names. Ive already got a server= line in my dnsmasq.conf which fixed full name resolution just fine. here is what I want to happen: dnsmasq gets request to resolve short name like andromeda (name of one of my windows servers) dnsmasq tries to find andromeda in either /etc/hosts or the dhcp leases and fails. dnsmasq can't forward to upstream servers an incomplete name, so it assumes that the windows service is handling that name, and checks. If windows can find a listing for andromeda fine, return it. If not, then fail. Possible? Thanks.
Re: [Dnsmasq-discuss] resolving short names
I have a small home network with several nodes, some static ips, others from dnsmasq's dhcp server. all have same netmask and class. Three of the nodes( two servers, one client) are Windows Active Directory domain members using the windows dns service for a different domain name. Most of the clients on the dnsmasq side are able to resolve short names just fine. I think you are trying to add too much complexity to this configuration. If dnsmasq is your dhcp server, then assign static addresses to the three Windows domain members, add entries in the /etc/hosts file for them, and be done with it. The Windows DNS server uses dnsmasq as its upstream server to allow the Windows domain members to resolve the names of the other nodes in your configuration. An alternate plan would be to use Windows DNS and Windows DHCP instead of dnsmasq. My guess is that this isn't ideal because the Windows domain isn't up 100% of the time. I have a similar configuration. My Windows domain is all virtual machines which are down unless I need to debug or research something domain related. Regards, Brad
