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:
Following architecture demonstrates Hub and VCN attachment with Infoblox deployed in Hub VCN
Infoblox Provisioning and Config
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
This configuration will forward all the traffic to the Custom DNS server (OCI Infoblox server).
Recommended by LinkedIn
Create DNS Listener in VCN DNS Resolver
Infoblox configuration related to OCI
Below diagram illustrate the dns record query flow
Note:
Reference:
Disclaimer: "The views expressed in this post are my own and do not necessarily reflect the views of Oracle."