DNS resolution on management network

What's the best practice for resolving DNS for your hosts on your management network? Hosting DNS on your vCenter server or routing DNS requests to your AD integrated DNS servers on a VM network?

Our enviroment has an isolated management network, hosts and VC only. VC is connected to VM network as well with firewall in between the VMs and the VC. Anyone had any issues having a primary zone hosted on your management network?

0 Kudos
2 Replies

With a small number of ESX I usually use static hosts file (inside ESX and VC).

But also I add name in DNS due to compliance, due for using VM console (that require DNS resolution).


**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos


Route requests through your management network firewall to your standard DNS server. No need to setup duplicate DNS servers.

Best regards, Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009
Now Available on Rough-Cuts: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing ESX and the Virtual Environment'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
[url=http://www.astroarch.com/wiki/index.php/Blog_Roll]SearchVMware Pro[/url]|Blue Gears[/url]|Top Virtualization Security Links[/url]|Virtualization Security Round Table Podcast[/url]

Edward L. Haletky
vExpert XIV: 2009-2022,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos