This provider updates a Microsoft DNS server.
It interacts with the server via PowerShell commands. As a result, DNSControl must be run on Windows and will automatically disable itself when run on non-Windows systems.
DNSControl will use
New-PSSession to execute the commands remotely if
computername is set in
creds.json (see below).
This provider will replace
ACTIVEDIRECTORY_PS which is deprecated.
NO_PURGEare in use.
Currently this driver disables itself when run on Non-Windows systems.
It should be possible for non-Windows hosts with PowerShell Core installed to execute commands remotely via SSH. The module used to talk to PowerShell supports this. It should be easy to implement. Volunteers requested.
ActiveDirectory_PS provider reads an
computername setting from
creds.json to know the name of the ActiveDirectory DNS Server to run the commands on.
An example DNS configuration:
If you were using the
ACTIVEDIRECTORY_PS provider and are switching to
MSDNS, make the following changes:
MSDNS in any
creds.json: Since unused fields are quietly ignored, it is
safe to list both the old and new options:
a. Add a field “dnsserver” with the DNS server’s name. (OPTIONAL if dnscontrol is run on the DNS server.)
b. If the PowerShell commands need to be run on a different host using a
pssession: "remoteserver", where
remoteserver is the name of the server where the PowerShell commands should run.
c. The MSDNS provider will quietly ignore
psout. Feel free to leave them in
creds.json until you are sure you aren’t going back to the old provider.
During the transition your
creds.json file might look like:
dnscontrol preview to make sure the provider works as expected.
If for any reason you need to revert, simply change
dnsconfig.js to refer to
ACTIVEDIRECTORY_PS again (or use
git commands). If you are reverting because you found a bug, please file an issue.
Once you are confident in the new provider, remove