---
title: "Configuring a Grid"
canonical: "https://docs.infoblox.com/space/nios85/35385169/Configuring%20a%20Grid"
format: markdown
---
You can configure an IPv4-only, IPv6-only, or a dual mode (IPv4 and IPv6) Grid, but the configuration example in this topic uses IPv4 addresses. The sections in this topic are:  


> Macro (toc)

In this example, you configure seven NIOS appliances in a Grid serving internal DHCP and DNS for an enterprise with the domain name corpxyz.com. There are four sites: HQ and three branch offices. A hub-and-spoke VPN tunnel system connects the sites, with HQ at the hub. The distribution and roles of the NIOS appliances at the four sites are as follows:

- HQ site (four appliances in two HA pairs):
  - HA Grid Master: Hidden primary DNS server
  - HA member: Secondary DNS server and DHCP server for HQ
- Site 1 (two appliances in an HA pair): HA member, secondary DNS server and DHCP server for Site 1
- Site 2 (one appliance): Single member, secondary DNS server and DHCP server for Site 2

> ⚠️ **Note**
> ⚠️ 
> ⚠️ When adding an Infoblox appliance to an existing Grid, you must first check whether the Grid is running the minimum required software release of the appliance. For information, refer to the document, *Minimum* *Required* *Release* *Software* *for* *Hardware* *Platforms*, that was shipped with your product.

To create a Grid, you first create a Grid Master and then add members. The process involves these three steps:

1. Configuring two appliances at HQ as the Grid Master. For more details, see the *Create the Grid Master* section.
2. Logging in to the Grid Master and defining the members that you want to add to the Grid; that is, you configure Grid member settings on the Grid Master in anticipation of later joining those appliances to the Grid. For more details, see the *Define Members on the Grid Master* section.
3. Logging in to the individual appliances and configuring them so that they can reach the Grid Master over the network and join the Grid. For more details, see the *Join Appliances to the Grid* section.

After creating the Grid and adding members, you use the *Data Import Wizard* to import DHCP and DNS data from legacy servers. For more details, see the *Import DHCP Data* and *Import DNS Data* sections.  
Finally, you transition DHCP and DNS service from the legacy servers to the Infoblox Grid members. For more details, see *Enable DHCP and Switch Service to the Grid* section.

*Network* *Diagram*   
 

> Macro (drawio)

# Cable All Appliances to the Network and Turn On Power

Cable the NIOS appliances to network switches. After cabling each appliance to a switch and connecting it to a power source, turn on the power. For information about installing and cabling the appliance, refer to the user guide or installation guide that ships with the product.

1. At HQ and Site 1, connect Ethernet cables from the LAN1 and HA ports on the appliances in each HA pair to a switch, connect the appliances to power sources, and turn on the power for each appliance.  
When connecting the nodes of an HA pair to a power source, connect each node to a different power source if possible. If one power source fails, the other might still be operative.
2. At Site 2, connect an Ethernet cable from the LAN1 port on the single appliance to a switch, connect the appliance to a power source, and turn on the power for that appliance.

# Creating the Grid Master

> ⚠️ **Note**
> ⚠️ 
> ⚠️ IPv6 addressing is fully supported on Infoblox Grid Masters, HA pairs and standalone HA pairs, and appliances.  
> ⚠️ Examples in the sections of this chapter use IPv4.

Configure two appliances at HQ to be the two nodes that make up the HA pair forming the Grid Master.

## Grid Master – Node 1

1. By using the LCD or by making a console connection to the appliance that you want to make Node 1 of the HA pair for the Grid Master, change the default network settings of its LAN1 port to the following:
  - **IP Address**: **10.0.1.6**
  - **Netmask**: **255.255.255.0**
  - **Gateway**: **10.0.1.1**
2. Connect your management system to the HQ network, open a browser window, and connect to *https://10.0.1.6*.
3. Log in using the default username and password **admin** and **infoblox**.
4. Review the End-User License Agreement and click **I** **Accept**.
5. Read about the *Infoblox Customer Experience Improvement Program* and choose whether to participate (opt in) or not participate (opt out) in the program. By default, participation is enabled. If you want to opt out of the program, select **To Opt-Out of the alert program, please click here**. For more information about the program, see *[Configuring the Customer Experience Improvement Program](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35751150/Setting+Login+Options#SettingLoginOptions-ConfiguringtheCustomerExperienceImprovementProgram)*[.](https://docs.infoblox.com/display/nios85draft/Monitoring+Tools#MonitoringTools-Cust_Exp_Improvement)
6. Click **OK**. The *Grid Setup* wizard appears.
7. On the first screen, select **Configure** **a** **Grid** **Master** and click **Next**.
8. Specify the Grid properties:
  - **Grid** **Name:** Enter **corpxyz**.
  - **Shared** **Secret:** Enter **Mg1kW17d**.
  - **Confirm** **Shared** **Secret:** Enter **Mg1kW17d**.
  - **Hostname:** Enter **ns1.corpxyz.com**.
  - **Type** **of** **Network** **Connectivity:** Select **IPv4** from the drop-down list.
  - **Is** **the** **Grid** **Master** **an** **HA** **pair?**: Select **Yes**.
9. Specify the network properties and click **Next**:
  - **Virtual** **Router** **ID:** Enter **143**.
  - **Required** **Ports** **and** **Addresses:** To set up the HA pair, enter the details in the table located at the end of this procedure:
10. **Enter a new password**: **1n85w2IF**. Retype it and click **Next**.
11. Then, complete the following:
  - **Time** **zone:** Select **(UTC – 8:00 Pacific Time (US and Canada), Tijuana**
  - Enable **NTP**, click the Add icon and enter the IP address of the NTP server: **10.120.3.10**
12. Click **Finish**. When you click **Finish**, the Infoblox GUI application restarts.

| Interface | Address | Subnet Mask (IPv4) or Prefix Length (IPv6) | Gateway | Port Settings |
| --- | --- | --- | --- | --- |
| VIP (IPv4) | 10.0.1.10 | 255.255.255.0 | 10.0.1.1 | Automatic |
| Node1 HA (IPv4) | 10.0.1.7 | 255.255.255.0 | 10.0.1.1 | Automatic |
| Node2 HA (IPv4) | 10.0.1.9 | 255.255.255.0 | 10.0.1.1 | Automatic |
| Node1 LAN1 (IPv4) | 10.0.1.6 | 255.255.255.0 | 10.0.1.1 | Automatic |
| Node2 LAN1 (IPv4) | 10.0.1.8 | 255.255.255.0 | 10.0.1.1 | Automatic |

## Grid Master – Node 2

1. By using the LCD or by making a console connection to the appliance that you want to make Node 2 of the HA pair for the Grid Master, change the default network settings of its LAN1 port to the following:
  - **IP Address**: **10.0.1.8**
  - **Netmask**: **255.255.255.0**
  - **Gateway**: **10.0.1.1**
2. In the login window, type **10.0.1.8** in the **Hostname** field.
3. Log in using the default username and password, **admin** and **infoblox**.
4. From the **Grid** tab, select the **Grid** **Manager** tab -> **Members** tab -> *member* checkbox.
5. Expand the Toolbar and click **Join** **Grid** and specify the following:
  - **Virtual** **IP** **of** **Grid** **Master**: **10.0.1.10**
  - **Grid** **Name:** Enter **corpxyz**
  - **Grid** **Shared** **Secret:** Enter **Mg1kW17d**
6. Confirm the configuration, and then on the last screen of the wizard, click **Finish**. The HTTPS session terminates, but the login window remains open.
7. In the login window, type **10.0.1.10** (the VIP address for the Grid Master) in the **Hostname** field.
8. Log in using the default username **admin** and the password **1n85w2IF**.
9. To check the status of the two nodes of the HA Grid Master, navigate to the **Grid** tab, select the **Grid** **Manager** -> **Members** tab. This panel lists the Grid members. Check the icon in the **Status** column of the Grid Master. The colors indicate the following:
  1. **Green**: The appliance has joined the Grid and is functioning properly.
  2. **Yellow**: The appliance is in the process of joining the Grid
  3. **Red**: The appliance has not joined the Grid.  
You can also use the CLI command set network to join an appliance to a Grid. Check that the status indicators are all green in the *Detailed Status* panel.

During the joining process, an appliance passes through the following four phases:

1. **Offline**: The state when a Grid member—in this case, the second node of the HA pair composing the Grid Master—is not in contact with the active node of the master.
2. **Connecting**: The state when an appliance matching a member configuration contacts the master to join the Grid and negotiates secure communications and Grid membership.
3. **Synchronizing**: The master transmits its entire database to the member.
4. **Running**: The state when a member is in contact with the master and is functioning properly.

> ⚠️ **Note**
> ⚠️ 
> ⚠️ Depending on the network connection speed and the amount of data that the master needs to synchronize with the member, the process can take from several seconds to several minutes to complete.

# Defining Members on the Grid Master

Before logging in to and configuring the individual appliances that you want to add to the Grid, define them first on the Grid Master. You can configure a Grid member in IPv4, IPv6, or a dual mode (IPv4 and IPv6), but the configuration example uses IPv4 addresses.

## HQ Site – HA Member

1. From the **Grid** tab, select the **Grid** **Manager** -> **Members** tab.
2. Expand the Toolbar and click **Add** -> **Add** **Grid** **Member**.
3. In the *Add* *Grid* *Member* wizard, complete the following and click **Next**:
  - **Member** **Type**: Select **Infoblox**.
  - **Host** **Name**: Enter **ns2.corpxyz.com**.
  - **Comment**: Enter **HQ Site - ns2.corpxyz.com**.
4. Enter the following information about the member that you are adding to the Grid and click **Save** **&** **Close**:
  - **Type** **of** **Network** **Connectivity**: Select **IPv4** from the drop-down list.
  - **High** **Availability** **Pair**: Select this option.
  - **Virtual** **Router** **ID**: **210**
  - **Required** **Ports** **and** **Addresses**:

|  |  |  |  |  |
| --- | --- | --- | --- | --- |
| **Interface** | **Address** | **Subnet Mask (IPv4) or Prefix Length (IPv6)** | **Gateway** | **Port Settings** |
| VIP (IPv4) | 10.0.2.10 | 255.255.255.0 | 10.0.2.1 | Automatic |
| Node1 HA (IPv4) | 10.0.2.7 | 255.255.255.0 | 10.0.2.1 | Automatic |
| Node2 HA (IPv4) | 10.0.2.9 | 255.255.255.0 | 10.0.2.1 | Automatic |
| Node1 LAN1 (IPv4) | 10.0.2.6 | 255.255.255.0 | 10.0.2.1 | Automatic |
| Node2 LAN1 (IPv4) | 10.0.2.8 | 255.255.255.0 | 10.0.2.1 | Automatic |

## Site 1 – HA Member

1. From the **Grid** tab, select the **Grid** **Manager** tab -> **Members** tab.
2. Expand the Toolbar and click **Add** -> **Add** **Grid** **Member**.
3. In the *Add* *Grid* *Member* wizard, enter the following and click **Next**:
  - **Member** **Type**: Select **Infoblox**.
  - **Host** **Name**: Enter **ns3.site1.corpxyz.com**
  - **Comment**: Enter **Site 1 - ns3.site1.corpxyz.com**
4. Specify the following information about the member that you are adding to the Grid and click **Save & Close**:
  - **Type** **of** **Network** **Connectivity:** Select **IPv4** from the drop-down list.
  - **High** **Availability** **Pair**: Select this option.
  - **Virtual** **Router** **ID**: Enter **111**.
  - **Required** **Ports** **and** **Addresses**:

|  |  |  |  |  |
| --- | --- | --- | --- | --- |
| **Interface** | **Address** | **Subnet Mask (IPv4) or Prefix Length (IPv6)** | **Gateway** | **Port Settings** |
| VIP (IPv4) | 10.1.1.10 | 255.255.255.0 | 10.1.1.1 | Automatic |
| Node1 HA (IPv4) | 10.1.1.7 | 255.255.255.0 | 10.1.1.1 | Automatic |
| Node2 HA (IPv4) | 10.1.1.9 | 255.255.255.0 | 10.1.1.1 | Automatic |
| Node1 LAN1 (IPv4) | 10.1.1.6 | 255.255.255.0 | 10.1.1.1 | Automatic |
| Node2 LAN1 (IPv4) | 10.1.1.8 | 255.255.255.0 | 10.1.1.1 | Automatic |

## Site 2 – Single Member

1. From the **Grid** tab, select the **Grid** **Manager** -> **Members** tab.
2. Expand the Toolbar and click **Add** -> **Add** **Grid** **Member**.
3. In the *Add* *Grid* *Member* wizard, enter the following and click **Next**:
  - **Member** **Type**: Select **Infoblox**
  - **Host** **Name:** **ns4.site2.corpxyz.com**
  - **Comment:** **Site 2- ns4.site2.corpxyz.com**
4. Specify the following information about the member that you are adding to the Grid and click **Next**:
  - **Type** **of** **Network** **Connectivity:** Select **IPv4** from the drop-down list.
  - **Standalone** **Member:** Select this option.
  - **Required** **Ports** **and** **Addresses:** Click the empty fields and enter the following information:
    - **Address:** Enter **10.2.1.10**.
    - **Subnet** **Mask** **(IPv4)** **or** **Prefix** **Length** **(IPv6)**: Enter **255.255.255.0**
    - **Gateway**: Enter **10.2.1.1**
    - **Port** **Settings**: Select **AUTOMATIC**.
5. Save the configuration and click **Restart** if it appears at the top of the screen.
6. Log out from the Grid Master.

# Join Appliances to the Grid

To complete the process of adding appliances to the Grid, log in to and configure each individual appliance so that it can contact the Grid Master.

## HQ Site – HA Grid Member (Node 1)

Make a console connection to the appliance that you want to make Node 1 in the HA pair, and then enter the following:  
`Infoblox > set network `   
` NOTICE: All HA configuration is performed from the GUI. This interface is used only to configure a standalone node or to join a Grid.`   
` Enter IP address: 10.0.2.6 `   
` Enter netmask : 255.255.255.0 `   
` Enter gateway address : 10.0.2.1 `   
` Configure IPv6 network settings? (y or n):n Become Grid member? (y or n): y `   
` Enter Grid Master VIP: 10.0.1.10 `   
` Enter Grid Name: corpxyz `   
` Enter Grid Shared Secret: Mg1kW17d `   
` New Network Settings: IP address: 10.0.2.6`   
` Netmask: 255.255.255.0`   
` Gateway address: 10.0.2.1`   
` Join Grid as member with attributes: Grid Master VIP: 10.0.1.10`   
` Grid Name: corpxyz`   
` Grid Shared Secret: Mg1kW17d`   
` WARNING: Joining a Grid will replace all the data on this node!`   
` Is this correct? (y or n): y `   
` Are you sure? (y or n): y`

The Infoblox application restarts. After restarting, the appliance contacts the Grid Master and joins the Grid as Node 1.

## HQ Site – HA Member (Node 2)

Make a console connection to the appliance that you want to make Node 2 in the HA pair, and then enter exactly the same data you entered for Node 1 except that the IP address is 10.0.2.8.  
After the application restarts, the appliance contacts the Grid Master and joins the Grid as Node 2, completing the HA member configuration for the HQ site.

## Site 1 – HA Grid Member (Node 1)

Make a console connection to the appliance that you want to make Node 1 in the HA pair at Site 1 and use the `set network` command to configure its basic network and Grid settings. Use the following data:

- **IP Address**: **10.1.1.6**
- **Netmask**: **255.255.255.0**
- **Gateway**:** 10.1.1.1**
- **Grid Master VIP**: **10.0.1.10**
- **Grid Name**: **corpxyz**
- **Grid shared secret**: **Mg1kW17d**

The Infoblox application restarts. After restarting, the appliance contacts the Grid Master and joins the Grid as Node 1.

## Site 1 – HA Grid Member (Node 2)

Make a console connection to the appliance that you want to make Node 2 in the HA pair at Site 1 and enter exactly the same data that you entered for Node 1 except that the IP address is 10.1.1.8.  
After the application restarts, the appliance contacts the Grid Master and joins the Grid as Node 2, completing the HA member configuration for Site 1.

## Site 2– Single Grid Member

Make a console connection to the appliance that you want to make Node 1 in the HA pair at Site 1 and use the set network command to configure its basic network and Grid settings. Use the following data:

- **IP Address**: **10.2.1.10**
- **Netmask**: **255.255.255.0**
- **Gateway**: **10.2.1.1**
- **Grid Master VIP**: **10.0.1.10**
- **Grid name**: **corpxyz**
- **Grid shared secret**: **Mg1kW17d**

The Infoblox application restarts. After restarting, the appliance contacts the Grid Master and joins the Grid.  
To check the status of all the Grid members, log in to the Grid Master at 10.0.1.10, and from the **Grid** tab, select the **Grid** **Manager** tab -> **Members** tab, select **10.0.1.10** and click the Detailed Status icon. Check that the status indicators are all green in the Detailed Status panel. As an appliance joins a Grid, it passes through the following phases: Offline, Connecting (Downloading Release from Master), Synchronizing, and Running.  
The Grid setup is complete.  
Note that depending on the network connection speed and the amount of data that the master needs to synchronize with the member, the process of joining a Grid can take from several seconds to several minutes to complete.

# Import DHCP Data

The Data Import Wizard is a software tool that you can download from the Infoblox Support site to your management system. With it, you can import data from legacy DHCP and DNS servers to NIOS appliances. In this example, you use it to import both DHCP and DNS data to the Grid Master at 10.0.1.10, which then uses the database replication mechanism to send the imported data to other Grid members. In the wizard, you also specify which Grid members serve the imported data. The wizard supports various types of DHCP formats, such as the following:

- ISC DHCP
- Lucent VitalQIP
- Microsoft
- Nortel NetID
- CSV (comma-separated values); you can also import IPAM data in CSV format. In this example, all the DHCP data is in standard ISC DHCP format.

## Importing DHCP Data for HQ and Site 2

1. Save the DHCP configuration file from your legacy DHCP server at 10.0.2.20 to a local directory.
2. Visit *[https://support.infoblox.com](https://support.infoblox.com+)*, log on with your support account, and download the *Data Import Wizard*. The *Data Import Wizard* application downloads to a container within a Java sandbox on your management system and immediately launches, displaying the *Welcome* page.
3. After reading the information in the left panel, click **Next**.
4. Select Import to Infoblox Appliance, enter the following, and then click **Next**:
  - **Hostname or IP address**: **10.0.1.10**
  - **Username**: **admin**
  - **Password**: **1n85w2IF**
5. Select the following, and then click **Next**:
  - What kind of data would you like to import? **DHCP/IPAM**
  - Which legacy system are you importing from? **ISC DHCP**
  - Which appliance will be serving this data? **10.0.2.10**
6. Type the path and file name of the DHCP configuration file saved from the legacy server, and then click **Next**.  
Or  
Click **Browse**, navigate to the file, select it, click **Open**, and then click **Next**.
7. In the *Global DHCP Configuration* table, double-click the *Value* cell for the *domain-name-servers* row, and change the IP addresses to **10.0.2.10**.
8. When satisfied with the data, click **Import**.  
You can view the status of the importation process and a summary report in the *Data Import Wizard* Log.
9. To enable DDNS updates, log in to the Grid Master, from the **Data** **Management** tab, select the **DHCP** tab, expand the Toolbar and click **Grid** **DHCP** **Properties**.
10. In the **DDNS** -> **Basic** tab of the *Grid DHCP Properties* editor, select **Enable** **DDNS** **Updates**.
11. Save the configuration and click **Restart** if it appears at the top of the screen.
12. To check the imported DHCP configuration file, from the **Data** **Management** tab, select the **DHCP** tab, -> **Members** tab -> **10.0.2.10** checkbox. Expand the Toolbar and click **View** **DHCP** **Configuration**.
13. In the DHCP configuration file, check that all the imported subnets are present, and navigate to the beginning of the file and check that you see the `ddns-updates on` statement. (If you see `ddns-updates
     off`, enable DDNS updates for the Grid as explained in steps 9-12.)

## Importing DHCP Data for Site 1

1. Repeat the steps in the *Importing DHCP Data for HQ and Site 2* section, saving the DHCP configuration file from your legacy DHCP server at 10.1.1.20, and importing it to the Grid Master at 10.0.1.10 for the member with IP address 10.1.1.10 to serve.
2. Check the imported DHCP configuration file by logging in to the Grid Master and from the **Data** **Management** tab, select the **DHCP** tab -> **Members** tab -> **10.1.1.10** checkbox. Expand the Toolbar and click **View DHCP Configuration**.

## Importing DHCP Data for Site 3

1. Repeat the steps in the *Importing DHCP Data for HQ and Site 2* section, saving the DHCP configuration file from your legacy DHCP server at 10.1.1.20, and importing it to the Grid Master at 10.0.1.10 for the member with IP address 10.3.1.10 to serve.
2. After the importation process completes, check the imported DHCP configuration file by logging in to the Grid Master and from the **Data** **Management** tab, select the **DHCP** tab -> **Members** tab -> **10.3.1.10** checkbox. Expand the Toolbar and click **View DHCP Configuration**.

# Import DNS Data

Using the *Infoblox Data Import Wizard*, import DNS data from the legacy hidden primary server at 10.0.1.5 to the new hidden primary server at 10.0.1.10 (the Grid Master). The three phases to this task detailed later in this topic are:

1. *Before Using the Wizard*:
  - Save the named.conf file from the legacy server to a file in a local directory on your management system.
  - Enable the legacy server to perform zone transfers to the NIOS appliance.
  - Configure three name server groups for the Grid and allow the Grid Master/hidden primary DNS server at 10.0.1.10 to receive DDNS updates from the Grid members at 10.0.2.10, 10.1.1.10, and 10.3.1.10. These members act as secondary DNS servers and DHCP servers.
2. *Using the Wizard*: Define the source, destination, and type of DNS data in the DNS configuration file (named.conf) that you want to import.
3. *After Using the Wizard*: Check the imported DNS configuration file.

In this example, all the DNS data is in BIND 9 format. The *Data Import Wizard* supports various types of DNS formats, such as the following:

- BIND 4, 8, and 9
- Microsoft
- Lucent VitalQIP
- Nortel NetID

## Before Using the Wizard

You must set up the legacy server and Grid Master before using the *Data Import Wizard*.

### Legacy Server

1. Log in to the legacy name server at 10.0.1.5 and save the named.conf file, which contains all the DNS settings that you want to import into the Infoblox name server, to a local directory on your management system.
2. On the legacy server, enable zone transfers to the NIOS appliance.

### Infoblox Grid Master – DDNS Updates

1. Log in to the Grid Master at 10.0.1.10, and from the **Data** **Management** tab, select the **DNS** tab -> **Members** tab -> **10.0.1.10** checkbox and select the Edit icon.
2. In the *Member* *DNS* *Configuration* editor, select the **Updates** tab -> **Basic** tab and enter the following:
  - Select **Override**.
  - Allow updates from: Click the Add icon and select **IPv4 Address**. Enter **10.0.2.10** in the **Name** field of the new row.
3. Click the Add icon again and add **10.1.1.10** and **10.2.1.10** as IP addresses from which you allow DDNS updates.
4. Save the configuration and click **Restart** if it appears at the top of the screen.

> ⚠️ **Note**
> ⚠️ 
> ⚠️ When all DNS servers are members in the same Grid, the members use database replication to synchronize all their data—including DNS zone data. You can change the default behavior so that Grid members use zone transfers instead. In this example, Grid members use database replication.

## Infoblox Grid Master – Name Server Groups

1. From the **Data** **Management** tab, select the **DNS** tab -> **Name** **Server** **Groups** tab.
2. Click the Add icon to open the *Add Name Server Group* wizard.
3. Enter the following:
  - **Name** **Server** **Group** **Name:** HQ-Group
4. Click the Add icon and add the following:
  - **Grid** **Primary**: **ns1.corpxyz.com**; **Stealth**: Select this checkbox.
  - **Grid** **Secondary**: **ns2.corpxyz.com**; **Grid replication (recommended)**: Select this checkbox.
5. Click **Save** **&** **New**.
6. Repeat steps 2 to 4 to create another group. Name it **Site1-Group**, and use **ns1.corpxyz.com** as the hidden primary server, **ns3.site1.corpxyz.com** as a secondary server, and Grid replication for zone updates.
7. Repeat steps 2 to 4 to create another group. Name it **Site2-Group**, and use **ns1.corpxyz.com** as the hidden primary server, **ns4.site2.corpxyz.com** as a secondary server, and Grid replication for zone updates.

## Using the Wizard

While progressing through the *Data Import Wizard*, you must define the source, destination, and type of DNS data that you want to import. You then make some simple modifications to the data and import it.

### Defining the Source, Destination, and Type of DNS Data

1. Launch the *Data Import Wizard*.
2. After reading the information in the left panel of the welcome page, click **Next**.
3. Select** Import to Infoblox Appliance**, enter the following, and then click **Next**:
  - **Hostname or IP address**: **10.0.1.10**
  - **Username**: **admin**
  - **Password**: **1n85w2IF**  
The *Data Import Wizard* Log opens in a separate window behind the wizard. Leave it open while you continue.
4. Select the following, and then click **Next**:
  - **What kind of data would you like to import?**: **DNS**
  - **Which legacy system are you importing from?**: **BIND 9**
  - **Which appliance will be serving this data?**: **10.0.1.10**
5. Select the following, and then click **Next**:
  - **What BIND 9 DNS configuration file would you like to use?**: Click **Browse**, navigate to the named.conf file you saved from the legacy server, select it, and then click **Open**.
  - **What type of BIND 9 DNS data do you want to import?**: **DNS zone information** and **DNS record data**
  - **Where is the BIND 9 DNS record data?**: **Zone transfer(s) from a DNS server**; **10.0.1.5**

The wizard displays two tables of data. The upper table contains global DNS server configuration parameters. The lower table contains zone configurations.  
The *Data Import Wizard* Log presents a summary listing the number of views, zones, and DNS records in the configuration file.

> ⚠️ **Note**
> ⚠️ 
> ⚠️ Only superusers can import A, AAAA, shared A, and shared AAAA records with a blank name. Limited-access users must have read/write permission to **Adding** **a** **blank** **A/AAAA** **record** to import A, AAAA, shared A, and shared AAAA records with a blank name, otherwise, the import operation might fail. You can assign global permission for specific admin groups and roles to allow to import A, AAAA, shared A, and shared AAAA records with a blank name. For more information, see *[Administrative Permissions for Adding Blank A or AAAA Records](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35785599)*.

### Modifying DNS Data

While importing data from the legacy DNS server, you cancel the importation of global configuration settings, and apply the name server groups you created when performing the task described in the *Before Using the Wizard* section, to the zones you want to import.

1. In the *Global DNS Configuration* table, select all rows by clicking the top row and then **SHIFT**+click the bottom row.
2. Right-click the selected rows to display the *Set* *Import* *Options* dialog box, select **Do** **not** **import**, and then click **Apply**.
3. In the *DNS Zones* table, clear the **Import** checkbox for the default view.
4. Select **corpxyz.com**, **lab.corpxyz.com** and all the corresponding reverse-mapping zones.  
**Tip:** You can use **SHIFT**+click to select multiple contiguous rows and **CTRL**+click to select multiple noncontiguous rows.
5. Right-click the selected rows, and then select **Set** **Import** **Options**.
6. In the *Set* *Import* *Options* dialog box, enter the following, and then click **Apply**:
  - **Set Zone Type**: No change
  - **Set Import Option**: No change
  - **Set View**: default
  - **Set Member**: HQ-Group master
7. Select **site1.corpxyz.com** and all the reverse-mapping zones with 1 in the second octet in the zone name (1.1.10.in-addr.arpa, 2.1.10.in-addr.arpa, 3.1.10.in-addr.arpa, and so on).
8. Right-click the selected rows, and then select **Set** **Import** **Options**.
9. In the *Set* *Import* *Options* dialog box, make the same selections as in *[6](#ConfiguringaGrid-bookmark665)*, but choose **Site1-Group** master from the **Set** **Member** drop-down list.
10. Similarly, select **site2.corpxyz.com** and all the reverse-mapping zones with 2 in the second octet in the zone name.
11. Right-click the selected rows, and then select **Set** **Import** **Options**.
12. In the *Set* *Import* *Options* dialog box, make the same selections as in *[6](#ConfiguringaGrid-bookmark665)*, but choose **Site2-Group** master from the **Set** **Member** drop-down list.

### Importing DNS Data

1. Click **Import**.  
The wizard imports the global DNS parameters and zone-specific configuration settings from the named.conf file and performs a zone transfer of the data from the legacy server.
2. Use the *Data Import Wizard* Log to monitor progress and review results.  
The log lists all the zones that the wizard imports and concludes with a total of all the successfully and unsuccessfully imported zones.
3. To close the *Data Import Wizard*, click **Exit**. This closes the *Data Import Wizard* Log as well.

> ⚠️ **Note**
> ⚠️ 
> ⚠️ If the wizard is unable to import a zone, an error message with an explanation appears in the log.

## After Using the Wizard

After you import data, you must restart services on the Grid Master and delete the A records for the legacy servers from the corpxyz.com zone. You can also confirm that the imported data is correct and complete by checking the DNS configuration and the forward- and reverse-mapping zones.

1. Log in to the Grid Master (10.0.1.10), select the **Grid** tab, expand the Toolbar, and then click the Restart Services icon.  
Note that when importing data through the wizard rather than entering it through the GUI, although the Restart Services icon does not change to indicate you must restart the service for the appliance to apply the new data, you must restart it on the Grid Master for the imported configuration and data to take effect.
2. To remove A records for the legacy servers, from the **Data** **Management** tab, select **DNS** tab -> **Zones** tab -> **corpxyz.com**.
3. Expand the **Records** section, select the following A records in the *corpxyz.com* zone, and then click the Delete icon:
  1. ns1 (for 10.0.1.5)
  2. ns2 (for 10.0.2.5)
  3. ns3.site1.corpxyz (for 10.1.1.5)
  4. ns4.site3.corpxyz (for 10.2.1.5)
4. Remove the respective A records for legacy servers from the *site1.corpxyz* and *site3.corpxyz* subzones.
5. To check the imported DNS configuration file, from the **Data** **Management** tab, select the **DNS** tab -> **Members** tab -> **10.0.1.10** checkbox. Expand the Toolbar and click **View** -> **View** **DNS** **Configuration**.  
If you do not see the imported DNS configuration file, ensure that you have enabled DNS and restarted the services.
6. Scroll through the DNS configuration log to check that each imported zone has an allow-update statement like the following one for the `10.1.10.in-addr.arpa` reverse-mapping zone:  
`zone "10.1.10.in-addr.arpa" in {`  
`   …`  
`      allow-update { key DHCP_UPDATER; 10.0.2.10; 10.1.1.10; 10.2.1.10; };`  
`    …`  
`    };`

# Enable DHCP and Switch Service to the Grid

Finally, you must enable DHCP service on the three Grid members at 10.0.2.10, 10.1.1.10, and 10.2.1.10, and switch DNS and DHCP service from the legacy DNS and DHCP servers to them.

1. Log in to the Grid Master (10.0.1.10) and from the **Data** **Management** tab, select the **DHCP** tab -> **Members** tab -> **10.0.2.10** checkbox. Expand the Toolbar and click **Start**.
2. Repeat step 1 to enable DHCP on 10.1.1.10 and 10.3.1.10.  
Note that you must start the DNS service, as described in *[Starting and Stopping the DNS Service](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35786027)*. The Grid members are ready to serve DHCP and DNS, and send DDNS updates.
3. Take the legacy DHCP and DNS servers offline.