I want to share some implementation details in the hope of evaluating how NS has to be deployed.
In NethServer we run dnsmasq as DNS service daemon. In a typical scenario it’s configured to only forward requests to a primary and a (optional) secondary upstream DNS servers. The local resolv.conf points to 127.0.0.1, so the localhost itself behaves exactly like any host in LAN that uses NethServer as DNS.
When NethServer joins an AD domain (being it local or remote, Samba or MS) DNS requests for the domain are sent to the AD DNS. This is configured by
In the case above, we join a NethServer (member) to another NethServer (dc): what is the DNS IP?
We could pick
- any IP address of dc green(s) interfaces, corresponding to dnsmasq that forwards requests to nsdc
- the IP address of nsdc container itself, corresponding to the samba4-dc instance
Both should work, but…
if we pick 1, the member server also can see any host defined in NethServer dc, from the server-manager DNS page. If it runs as DNS/DHCP server this is desirable, but I don’t know if this leads to problems for AD!
if we pick 2, we are surely more compliant with AD, but we lose extra DHCP/DNS records set on the server-manager