NethServer Version: 7.5.1804
I’ve got a NethServer Primary DC up and running beautifully overall. I have two problems I’d like help with and one direct question. All of the actions described hereafter are executed via Windows 10’s RSAT DNS, ADUC, and ADSI Edit (while exploring potential permissions issues).
Automatic PTR Record creation / update.
This doesn’t seem to be happening by default. If I manually create the reverse lookup zone and create an entry for a server already listed in a forward lookup zone they also do not seem to become associated by default. What’s up? Must I tweak something to get automatic PTR creation / update working? I didn’t see anything about this in the documentation (though I’d love to be shown otherwise!).
I created an administrative user who is included in all default administrative groups (Ent. Admins, Schema Admins, DnsAdmins, etc). I then created a few new DNS domains for testing, nested a few inside those, and then attempted a deletion. It seems even if that user has full control over the object (including ownership) that god-level user is disallowed from deleting the object. Might be a disconnect between linux / windows (wherein the god-level AD user also needs to be a sudoer on the nsdc container)? Just a guess. Thoughts? The real quirky bit is I can delete entire zones even though I cannot delete the individual domains underneath.
I’d prefer to run a split-zone DNS where my internal DNS domain is the same as my external. Normally I’d create a few CNAMEs and install nginx on the DC to forward http/https requests to the same place. Is there a recommended procedure for this when using NethServer/nsdc? I’m comfortable with the administrative overhead. Just looking for best practices for the less-than-best-practice.
Thank you in advance! <3
P.S. I’m not afraid of reading. If someone has brought up these questions before or there are answers documented somewhere feel free to link me.