Entries are not passed to NethServer’s DNS (they do not show up in the web GUI). Clients may join the AD Domain through the nsdc DNS. Pointing clients to nsdc for DNS yields forward lookup entries. All of the aforementioned entries are forwarded to the nsdc, however AD DNS passthrough doesn’t work (in other words if I attempt to join the domain while using NethServer’s DNS the join will fail). Reverse lookup entries are only made for clients whose IP address reside in the same subnet as NethServer’s. These entries can be seen in NethServer’s web GUI. Would you let me know if I’ve misunderstood something?Ĭonfiguring NethServer (dnsmasq) as a DHCP server and then pointing clients to NethServer for DNS/DHCP yields both forward and reverse lookup entries. I’m going to summarize the content of that thread here to make sure I understand.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |