---
title: "Use vNIOS Instance as Primary DNS for VPC"
canonical: "https://docs.infoblox.com/space/DeploymentGuidevNIOSforAWS/736297525/Use%20vNIOS%20Instance%20as%20Primary%20DNS%20for%20VPC"
format: markdown
---
> Macro (toc)

Infoblox vNIOS for AWS instances can be used as the primary DNS servers for AWS VPC. This allows you to extend your enterprise DNS and RPZ services into your AWS networks.

### **Setup DNS Service**

First, we will configure basic DNS service on the Infoblox vNIOS for AWS instance. In this guide we will configure the server for both authoritative and recursive DNS; in production environments you will likely want to separate these roles on multiple appliances.

1. Login to your vNIOS for AWS instance Grid Manager GUI.
2. Navigate to the **Grid → Grid Manager → Services **tab.
3. Click on the **DNS** service.

![image](media://87ee7f70-34fc-44aa-bbbf-1e2a9f8003cf)

4. Select the checkbox next to your vNIOS member.
5. Click the  start button to start the DNS service.

![image](media://6b0b069e-57cf-4866-ae3b-0b5dd4e6f164)

6. Click **Yes** in the popup window to confirm.

![image](media://ab8e05a5-99b8-475e-a719-4c508105bb52)

7. Once the service is started, open the dropdown next to Edit in the right-hand menu.
8. Select **Grid DNS Properties**.

![image](media://dd995bc8-f715-4cad-a7a6-b4c2227caabf)

9. In the Grid DNS Properties window, select the **Queries** tab.
10. Optionally, change Allow queries to **Set of ACEs**.
11. Use the  add dropdown to select **IPv4 Network**.

![image](media://e7493166-c540-4643-8df5-3dee3e089f11)

12. For **Address** enter the network prefix for your VPC. For example: **172.17.0.0**.
13. Use the **Netmask** slider to select the correct mask size. For example: **/16**.
14. Click **Add**.

![image](media://011ae134-2464-43c4-b948-a3075be8ffcc)

15. Scroll down and select **Allow recursion**.
16. Select **Set of ACEs**.
17. Use the  add dropdown to select **IPv4 Network**.

![image](media://2f3e1914-a4fa-440d-8695-7a44cac01686)

18. For **Address** enter the network prefix for your VPC. For example: **172.17.0.0**.
19. Use the **Netmask** slider to select the correct mask size. For example: **/16**.
20. Click **Add**.

![image](media://011ae134-2464-43c4-b948-a3075be8ffcc)

21. Click **Save & Close**.
22. In the Warning window, click **Yes**.

![image](media://e56d1d64-675b-4060-a134-a811245638ec)

23. Click **Restart** in the banner that opens in the top of the window.

![image](media://d37b89bd-4724-4a2a-9950-01989bb053c7)

24. Click the **Restart** button in the Restart Grid Services window.

![image](media://27d60777-1b71-425d-8437-19f61afe0a2d)

#### **Add DNS Zone**

1. To add an authoritative DNS zone, navigate to the **Data Management → DNS → Zones **tab.
2. Use the  add dropdown to select **Authoritative Zone**.
3. On Step 1 of the Add Authoritative Zone Wizard, select **Add an authoritative forward-mapping zone**.
4. Click **Next**.

![image](media://6b6e6a62-f9fa-4f68-854b-2f4c81d11db0)

5. On Step 2 enter a name for your DNS zone.
6. Click **Next**.

![image](media://06dcec97-f7d1-4b53-bf62-a285626de16f)

7. On Step 3 select **Use this set of name servers**.
8. Use the  add dropdown to select **Grid Primary**.

![image](media://515cf965-0749-47c1-a5a2-a6e07a31b7fb)

9. Click **Select**. The single member of this Grid will automatically be selected.
10. Click **Add**.

![image](media://dd27d758-db67-49e9-9d69-4004789676ee)

11. Click **Save & Close** to create the new zone. Or click **Next** to proceed to optional steps.

![image](media://faf8d502-bf19-410a-b3dc-d966b1f360e1)

12. Click **Restart** in the banner that opens at the top of the window.
13. Click the **Restart** button in the Restart Grid Services window.

### **Create AWS DHCP Options Set**

AWS VPCs use DHCP options sets to specify optional configurations such as a default domain name or the DNS servers your instances should use. We will use an options set to make the Infoblox vNIOS for AWS instance the primary DNS server for a VPC. DHCP options sets cannot be modified after creation, so we will start by creating a new DHCP options set.

1. In the AWS Management Console, Use the Services menu to navigate to **VPC **under Networking & Content Delivery.
2. From the VPC menu, click on **DHCP Options Sets**.

![image](media://ddd862ab-8d9e-4285-a169-f60ec744500c)

3. Click **Create DHCP options set**.
4. Enter a name for your option set.
5. Under Domain name servers, enter the private IP address of your vNIOS for AWS eth1 (LAN1) interface.

![image](media://7791eaaa-adad-4875-9ab0-3392fe7351ee)

6. Scroll down and click **Create DHCP options set**.

![image](media://8080ee96-b396-41bf-a02c-f2baccfac7c5)

7. To assign this DHCP options set to your VPC, select **Your VPCs** in the menu.
8. Select your VPC.
9. Use the Actions dropdown menu to select **Edit VPC settings**.

![Graphical user interface, text, application, email

Description automatically generated](media://622b5ae4-364e-443e-ab42-f2a357c3ecb5)

10. Use the dropdown menu for DHCP options set to select the new options set you created.

![Graphical user interface, text, application, email

Description automatically generated](media://5c7f4853-1773-4782-96a7-d2793dfbab2d)

11. Scroll down to click **Save**.

*Note: Any new VM instances you create in this VPC will use your Infoblox vNIOS for AWS appliance for DNS resolution. Existing VM instances must be rebooted to apply this change.*