Ping Domain returns strange IP's...?

[abillybob]

Hi All

 

Hoping you can help me as I'm pulling my hair out with this one.

 

I've got a situation where pinging our domain such as workplace.local returns an IP of 192.168.33.46 when our domain controller is on 192.168.33.2.

 

I've looked under that .46 IP on our DNS but it's some kind of Sales-Admin computer so dosen't look strange to me and I'm confused as to how it's resolving to this IP if in our DNS it indicates this is a totally different name!!

 

It has now somehow changed and it now shows 192.168.33.1 as pic.local but this is actually an old Domain Controller one that hasn't got DNS installed and it's name is totally different to workplace.local its terminalserver.workplace.local.

 

It's causing me issues because if you apply a group policy it obviously pulls this from workplace.local DNS name but that isn't the case because the IP that it's resolved to keeps changing.

 

Can anyone help or point me in the right direction of where to look?

 

Thanks a lot all

abillybob

[abillybob]

An nslookup does this

 

[abillybob]

Sorry all me being a dosy!! Fixed, needed to remove (same as parent folder) under each IP

[abillybob]

Ok so it did work but now after about 10 minutes 192.168.33.1 has appeared again, the other aren't there but my god this is annoying! Anyone know why this is happening?

[dapaulio]

Firstly need to determine is this just one pc or everypc. This could be as simple as individual pc issue to a full network dns issue. Do you get the same results from other computers on the domain?

If no First of all try from a cmd prompt on an affected pc ipconfig /flushdns

 

check your hosts file on affected pc( open with notepad). Any weird entries

%windir%\system32\drivers\etc

 

If across all computers on network ... Was your dc promoted into the domain maybe under that ip which I assume is within the dhcp scope then changed to a static address .2 afterwards?

Also were your legacy dc demoted out of the domain and dns properly migrated

Check all your dcs have a static ip and dns address assigned to the actually dns server ip on your network.

Also check additional dns ip in the advanced button of ip4 adapter properties config for any additional ips that may have been added for whatever reason. There are mixed views on the best practice when setting dns priority on multi dc domain. Some say and Personally I have 127.0.0.1 As primary dns address and my secondary dns set to the other dc. Others say it should be the other way around.

 

Check reverse dns lookup under the ip .46 to see if there are two or more entries under that ip.

 

I mean no disrespect by this comment but At this point I would seriously assess your ability to deal with this issue before making any dns changes as with all dns issues you can easily make things far worse.