Case Study - Infoblox As custom DNS Solution in OCI

Case Study - Infoblox As custom DNS Solution in OCI

Today, we delve into an exciting topic: utilizing an Infoblox DNS server as the primary DNS server for OCI. This approach offers a range of benefits and provides an efficient solution for name resolution. Let's explore.

By default, each VCN in OCI has its own resolver, enabling name resolution within the VCN and the Internet. However, if you need to resolve names on-premises or in another VCN, you must explore various options. These options include adding a private view of another VCN to the VCN DNS resolver, creating forwarders and listeners based on on-premises or other region records, and potentially adding Private Views or Zones depending on specific requirements. Alternatively, you could deploy your DNS solution or use hostnames, but these options may not be scalable.

In this particular case, the customer wanted to use their on-premises Infoblox server as the primary DNS for all named queries. They had multiple in-house domains, external partner domains, and separate public DNS records with multiple providers, and they did not want to configure separate routing from OCI. Additionally, they did not want to maintain ANY records for OCI resources.

The solution implemented in this scenario consists of the following key components:

  1. On-premises Infoblox server as Master Grid having all records
  2. OCI based Infoblox servers to cache named records and provide low latency for querying record
  3. VCN DNS Listener under VCN private view to query back OCI related records.

Following architecture demonstrates Hub and VCN attachment with Infoblox deployed in Hub VCN

Article content
Fig: Infoblox DNS setup in OCI

Infoblox Provisioning and Config

  • Provision the Infoblox with Marketplace image. Refer this guide.
  • Create another VNIC for the VM with “Skip source/destination check” option
  • Provision the VM and update the license type from cloudshell console. Also configure Master Grid’s address. Once Infoblox server is connected to Master Grid, it will add OCI Infoblox server as child node.

Infoblox also forwards internet traffic to firewall (untrust) or internet using NAT/Internet Gateway.

Update DHCP Option in OCI

Update the VCN’s Default DHCP option to use

  • Type as “Custom Resolver”
  • Add Infoblox Secondary VNIC IP under DNS Server Address

Article content
Fig: Editing DHCP Option

This configuration will forward all the traffic to the Custom DNS server (OCI Infoblox server).

Create DNS Listener in VCN DNS Resolver

  • Navigation – VCN Private resolver> Endpoints> Type “Listener”> Subnet of your VCN

Article content
Fig: VCN DNS Resolver listener

  • Update the Listener address into Infoblox for Forwarding all OCI related search zones.
  • Attach respective NSG in case traffic is maintained by means of NSG rules.
  • In the same region, private DNS views of all VCN are required to be added into the DNS resolved where Listener has been created for receiving traffic from Infoblox.
  • For multi region setup, Infoblox is managing to send OCI related traffic to respective Listener from another region. Also, another region can have local Infoblox server for reducing latency.

Infoblox configuration related to OCI

  • Configure the search zones based on VCN FQDN (like hub.oraclevcn.com) and so other VCN private zones, along with custom zones
  • Search zones based upon OCI zones will forward the traffic to OCI DNS Listener
  • Search zones based upon internet will forward traffic to Firewall or Internet Gateway so to send Global DNS Providers.

 Below diagram illustrate the dns record query flow


Article content
Fig: Dataflow named query


Note:

  • Failure or downtime in Infoblox server can cause disruption of DNS service. It is recommended to deploy secondary Infoblox for HA.
  • Any newly added VCN may require addition of the search zone in Infoblox. Flat oraclevcn.com search zone in Infoblox can cause instability in case of using multi-region set up
  • It is highly recommended to use OCI default DNS service. In unavoidable case, use custom DNS solution with limited specific search domains.

Reference:

 

Disclaimer: "The views expressed in this post are my own and do not necessarily reflect the views of Oracle."

To view or add a comment, sign in

More articles by Abhinandan Gajar

  • Intra-Hub VCN Routing - Best Practice

    In the typical hub-spoke architecture, a network firewall is deployed into the hub VCN and all other applications…

Insights from the community

Others also viewed

Explore topics