Without it, the command will create a new zone data file that will overwrite the contents of the backup file.Īfter adding the zone to the DNS server, you can convert it to an AD-integrated zone by running:ĭnscmd /zoneresettype /dsprimaryĪt this point, you can then enable secure dynamic updates for the zone by running: Use the /load switch to tell the command to load the configuration from the existing file.
Here, note that the backup file needs to reside in the %systemroot%\system32\dns folder for it to be properly discovered. For example, to recover my zone, I’d run:ĭnscmd /zoneadd /primary /file /load The only catch with this approach is that if you’re looking to recover an AD-integrated zone, you need to add the zone as a primary first and then convert it to AD-integrated. If you need to re-create a new zone from the export file, you’ll find that you can do this by using dnscmd.exe with the /zoneadd switch. Note that the command doesn’t overwrite existing files, so if you’re including it with a backup script, be sure to move the file to an alternate location after the export completes, or to rename or delete the current backup file before you run a new dnscmd /zoneexport job. This command writes a copy of the zone to the %systemroot%\system32\dns\backup\ file. To back up the zone locally on a DNS server, you’d run:ĭnscmd /zoneexport backup\ To back up any DNS zone with dnscmd.exe, you just need to use the /zoneexport switch with the command. For these zones, the support tool dnscmd.exe can get the job done. Unfortunately, the process isn’t as simple for Active Directory-integrated DNS zones. Xcopy %systemroot%\system32\dns d:\backups\dns /y This command would back up the contents of the default DNS folder to the “D:\backups\dns” folder: You can use the xcopy command to back up all zone text files on a DNS server. With DNS, backing up primary and secondary zones independent of the system state is a pretty simple process.
0 kommentar(er)
