Advanced DNS config - Amahi DNS as BIND secondary of AD DNS
Posted: Thu Sep 01, 2011 8:23 am
i have setup the Amahi server on my local network. for testing purposes, there is also a Windows 2008 AD infrastructure in the same network. each uses their own "x.local" domain name.
i have added in the Amahi's domain name as a Secondary zone to Microsoft's AD DNS, by pointing at the appropriate Amahi IP. clients are able to resolve addresses in the Amahi domain.
i am now editing the /etc/named.conf (actually the /etc/named.conf.local) to have the opposite occur, so Amahi domain clients are able to lookup my MS AD DNS too.
i have added the following to the bottom of the above config file:
on the MS AD DNS server, i have added a tick to the "BIND secondaries" option on the DNS server's properties and also allowed Zone Transfers to "any server".
restarting the Amahi DNS service after this, does not import this data and clients unable to do lookups.
if i add the new zone definition directly to the /etc/named.conf, the Amahi DNS service is unable to start.
any clues or help? anyone achieved this?
many thanks...
i have added in the Amahi's domain name as a Secondary zone to Microsoft's AD DNS, by pointing at the appropriate Amahi IP. clients are able to resolve addresses in the Amahi domain.
i am now editing the /etc/named.conf (actually the /etc/named.conf.local) to have the opposite occur, so Amahi domain clients are able to lookup my MS AD DNS too.
i have added the following to the bottom of the above config file:
Code: Select all
zone "redswitch.local" {
type slave;
file "slaves/redswitch_slave.conf";
masters { 192.168.1.201; } };
};restarting the Amahi DNS service after this, does not import this data and clients unable to do lookups.
if i add the new zone definition directly to the /etc/named.conf, the Amahi DNS service is unable to start.
any clues or help? anyone achieved this?
many thanks...