asked on

Physical server has a DNS IP that does not exist in our domain

I just noticed that a server that is obtaining it's IP and DNS automatically has a DNS IP as it's alternative that doesn't exist in our AD.

I did an ipconfig /flushdns, then ipconfig /all and it still has the incorrect DNS.

Where should I begin to locate the issue?

ASKER CERTIFIED SOLUTION

Cliff Galiher

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

J.R. Sitman

ASKER

In my post I mentioned it is obtaining the IP/DNS automatically, hence via DHCP.

Thank you for pointing me in the right direction. The incorrect DNS IP was coming from one of the DHCP server scopes. I corrected it. I've done multiple flushdsn on the server that has the wrong alternate DNS IP, put it is still showing the incorrect IP. Shouldn't flushdns correct it immediately.

SOLUTION

Cliff Galiher

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

J.R. Sitman

ASKER

Got it. Can I do that while the server is being used? Also can it be done remotely?

Cliff Galiher

Usually no and no. The process usually resets connections (including the remote connection) and often leaves you in a place where you cannot issue the /renew.

J.R. Sitman

ASKER

Thanks. I'll reboot it tomorrow.

J.R. Sitman

ASKER

Thanks