Porting Data Files from Other DNS Servers

You can use the boot, zone, cache, and other files from non-Microsoft RFC-compliant DNS servers. To do this, you must install these files in the \%systemroot\System32\DNS directory, and then stop and restart the DNS server.

Before installing files from other DNS servers on a Microsoft DNS server, you must edit the file name and directory location text in the ported files and make additional changes as described in this section.

The boot file will be used to load the data files you want to port into a Microsoft DNS server. A boot file is actually a file that controls the startup behavior of DNS servers running under a BIND implementation of DNS. It is a BIND-specific feature and not a requirement of the DNS RFCs. Microsoft DNS server's ability to use a boot file on initial startup is provided to support migration of data from BIND-based DNS servers to Microsoft DNS servers.

Although Microsoft DNS server will support a boot file, you must install the edited boot file before using DNS Manager. Starting DNS Manager configures the Microsoft DNS server to use the Windows NT Server Registry instead of the boot file.

If you need port data files after starting DNS Manager, you must change the value of the EnableRegistryBoot parameter from 1 to 0. The EnableRegistryBoot parameter is located in the following key:


\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters

To change the value of the EnableRegistryBoot parameter

1. Click Start, and then click Run.

2. In Open, type regedit, and then press ENTER.

3. Open the following key folder:


\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters

4. Select the EnableRegistryBoot parameter in the right pane of the Registry Editor, and then select Edit.

5. Click Modify, and type 0.

6. Click OK, and return to the menu bar and click Edit.

7. Select New, and then click DWORD Value.

8. Type 0 in the value box, and press enter.

9. Stop and restart the Microsoft DNS server by using Services in Control Panel.

The following table describes the format of boot file commands. You can use any text editor to edit or create a boot file. Commands must start at the beginning of a line and no spaces may precede the commands. This table shows the order in which the Microsoft DNS server supported boot commands must appear in the file, and gives the syntax for each command.

Table 9.4 BIND Boot File Commands

Description

Syntax

Specifies a directory where other files referred to in the boot file can be found.

directory <directory>

Specifies a file used to help the DNS service contact DNS servers for the root domain. This command and the file it refers to must be present.

cache <filename>

Specifies a domain for which this DNS server is authoritative, and a database file which contains the resource records for that domain in the zone file. Multiple primary command records can be entered in the boot file.

primary <domain> <filename>

Specifies a domain for which this DNS server is authoritative, and a list of master server IP addresses from which to attempt downloading the zone information.

secondary <domain> <hostlist> <local filename>