Change DNS Servers for Vsphere client


We have setup VmWare on our network and are slowly moving our Servers from 'Physical' to ‘Virtual’.  We have a planned rollout process and only have a few VmWare applications servers in place.  We have:

1.  1 Vcenter server
2.  1 Microsoft application Server
3.  1 Microsoft Exchange Server
4.  1 Domain Controller/DNS Server

.. in place and are working just fine.  

My question is how can I connect to the host VmWare Servers and change the DNS Entries, when the vsphere client is not accessible?

The problem is that these 2 VmWare hosts have static IP addresses on them.  And the Primary DNS Server (was also a Domain Controller) and I demoted that domain controller last evening.  Now I moved the Global Catalog settings and FSMO roles to 2 different domain controllers.  And those other 2 domain controllers are DNS servers as well.  

The old Domain controller is still turned on; but, today every PC, in the Domain, that had that (Demoted) Domain Controller’s IP address listed in the Primary DNS Slot needed to have that changed to a different domain Controller/DNS server.  Then those rouge PC’s worked.  I already changed the vast majority,of PC's, before I demoted the old Domain Controller/DNS Server; but, there were a few exceptions.  As soon as I put a different domain controller/DNS server in the primary DNS field (TCP/IP settings) then that worked for those PC’s.  Even though they had a secondary DNS server setup as well.  Anyway....

Today, Exchange works, Windows logon and file permissions work; but, I cannot logon to the Vshere client.  I know the hosts are setup with the Primary DNS Server as the old Domain Controller/DNS Server.   How can I change the DNS Server Settings on the VmWare Hosts servers, when the Vsphere client is unavailable?

Please see the screen shots below.

PkafkasNetwork EngineerAsked:
Who is Participating?
craigothyConnect With a Mentor Commented:
Is your vcenter server running as a vm?  You can point the vsphere client at the ip address of the esx physical host and manage it that way.
Paul SolovyovskyConnect With a Mentor Senior IT AdvisorCommented:
As stated above you can use ip address or add a record in your host file on the machine that you're trying to access from.

Another option is to RDP into the vCenter server system and access the VI client from there
PkafkasNetwork EngineerAuthor Commented:
I looked over my notes and I found the 'root' username and password.  that works, I can logon with the root username and password.  See the screen shotthis iswhere i cna change the DNS entries.

I also typed in the Ip address of the host and not teh Hostname.  So the only questions is if I change this will I need to restart the host?  The I hope that will not screw up the vm's.
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

Paul SolovyovskyConnect With a Mentor Senior IT AdvisorCommented:
No you will not.

As you see you will only need to reboot if you change hostname or domain.
Hi Pkafkas,

There is nothing wrong with your vSphere client or any other config.  As you have stated above, your VMware ESX host servers have static IP addresses. This effectively means that you need to create "A" records of these servers in your DNS servers/ DC's. Thsi will then enable your client machine to automatically see your VMware ESX servers.

The alternative to this is to add the server details for your VMware host to the hosts file in your client machine (from where you are trying to launch the vsphere client)

The effective way to test if your client machine can see the servers by their names is to do an nslookup for the ESX hostname i.e from command prompt , just run "nslookup wcdvcenter". If this returns the correct IP address, we might have to look at other ways of resolving this. but if it doesn't return the right values, make the changes I have suggested above and then test again.
PkafkasNetwork EngineerAuthor Commented:
I just logged on to the ESX box as the 'root' username and cahnged the DNS.  That solved the problem.  The DNS server needed to be changed the ESX box where the vsphere client was being hosted on.

The vsphere client was working just fine until I demoted the old DNS Server.  I just did not change the primary dns server from the old DNS Server to a newer active one.
All Courses

From novice to tech pro — start learning today.