WIndows FQDN conflict with Linux FQDN

I am running a Windows 2008 R2 on a WIndows VMWare VM

I am trying to install Active Directory on that VM

From a separate Linux machine, I run the following command:

    # host 10.14.2.5
    field.abc.com

Open in new window


From the Windows VM, I run the following command in the powershell

    PS C:\t> (gwmi WIN32_ComputerSystem).Name + "." + (gwmi WIN32_ComputerSystem).Domain
    field.DEPTA

Open in new window


So both Linux and agree on the short single name (field), but they disagree on the FQDN

How can I change the Windows VM to have the FQDN that Linux thinks is the correct FQND

    field.abc.com

Open in new window

(Note: When I try to install AD with the Linux version of the FQDN, it says there is a conflict)

Thanks
Anthony LuciaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Svet PaperovIT ManagerCommented:
The FQDN of a Windows machine is determined by the AD Domain.

If you want to add it to an existing domain, it will take FQDN of computer_name plus domain_name.extension, which is abc.com in your example.

If you need to create a new Windows domain to much the information returned by your Linux host, the domain must be abc.com.

Linux host command performs a simple DNS lookup and returns what it finds in its DNS server. It does not query the Windows host.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mr TorturSystem EngineerCommented:
Hi,
I agree with Svet Paperov. The answer to your commands depends only of your DNS server.
But AD controller will be its own DNS server (maybe with a alternate dns server), while maybe your Linux has another DNS server that does not know your Windows VM.

To answer your main question I would say you must modify your DNS entry for your Windows VM in the Linux DNS server.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.