VMware Cloud Community
rmarul
Contributor
Contributor

ESXi 5.1 cuts off DNS subdomain on resolution.

Hello,

I currently have a problem with DNS on my ESXi 5.1 machines. For some reason, they cut the sub domain off when you try to do resolution on the ESXi server. It works correctly everywhere else. It also works correctly on my ESX 4.1 machines.

My DNS schema looks like the following..

"server1.room1.building.local"

If you do this from any other machine in the network, other than the ESXi 5.1 servers, you get the correct resolution. If you attempt to resolve this from the ESXi 5.1 servers, you only get "server1.building.local". For some reason, resolution on the ESXi 5.1 servers cuts off the sub domain. This ONLY happens when you resolve from the ESXi server itself, everyone else on the work can resolve it correctly as "server1.room1.building.local.

Has anyone else seen similar behavor?

Thanks in advance!

0 Kudos
4 Replies
JCMorrissey
Expert
Expert

Hi,

Be worth running through the checklist in the enclosed KB  to make sure everything is in place

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100373...

Many tx

Please consider marking as "helpful", if you find this post useful. Thanks!... http://johncmorrissey.wordpress.com/
TomHowarth
Leadership
Leadership

Verify that the host's Domain is correctly configured.

Tom Howarth VCP / VCAP / vExpert
VMware Communities User Moderator
Blog: http://www.planetvm.net
Contributing author on VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment
Contributing author on VCP VMware Certified Professional on VSphere 4 Study Guide: Exam VCP-410
rmarul
Contributor
Contributor

Any chance you could provide a bit more input?

It's a Windows DNS server. The forward/reverse lookups work fine everywhere but the ESXi 5.1 servers. I checked on Windows 7, Server 2003, Server 2008 and several flavors of Linux. Even the ESX 4.1 servers resolve everything correctly. I assume it's something unique to ESX 5.1.

0 Kudos
rmarul
Contributor
Contributor

This provided me with a semi-fix, if I comment out the line with the bad information in /etc/hosts, it'll resolve correctly. Any idea how this file is generated? I could probably just include this fix in my ks.cfg and be done with it.

0 Kudos