WARNING: This provider is deprecated and will eventually be removed.
Please switch to MSDNS. It is more modern and reliable. The
creds.json fields changed names; otherwise it should be an
This provider updates an Microsoft Active Directory server DNS server. It interacts with AD via PowerShell commands that are generated and executed on the local machine. This means that DNSControl must be run on a Windows host. This driver automatically deactivates itself when run on non-Windows systems.
For debugging and testing on non-Windows systems, a “fake PowerShell” mode can be used, which will activate the driver and simulate PowerShell as follows:
adzonedump.ZONE.json(where “ZONE” is replaced with the zone name). When “fake PowerShell” mode is enabled, the PowerShell command is not run, but the
adzonedump.ZONE.jsonfile is read. You must generate this file ahead of time (often on a different machine, one that runs PowerShell).
dns_update_commands.ps1and the system assumes they executed.
To activate this mode, set
"fakeps":"true" inside your credentials file for the provider.
ActiveDirectory_PS provider reads an
ADServer setting from
creds.json to know the name of the ActiveDirectory DNS Server to update.
If you want to modify the “fake powershell” mode details, you can set them in the credentials file:
An example DNS configuration:
To generate a
adzonedump.ZONE.json file, run
dnscontrol preview on a Windows system then copy the appropriate file to the system you’ll use in “fake powershell” mode.
adzonedump.ZONE.json files should be UTF-16LE encoded. If you hand-craft such a file on a non-Windows system, you may need to convert it from UTF-8 to UTF-16LE using:
iconv -f UTF8 -t UTF-16LE <adzonedump.FOO.json.utf0 > adzonedump.FOO.json
If you check these files into Git, you should mark them as “binary” in