Hello Symantec community. This is a strange one that has suddenly started to happen on our SEPM servers. When I go to push a client via the SEPM console, it does not find the correct PC name or IP address on our network. It actually resolves to an entirely different PC.
For example, I'll use nslookup from the SEPM server to look up XXXXX PC name and I confirm in DNS that it is indeed xxx.xxx.xxx.xxx IP, yet SEPM resolves to an entirely different PC name. If I try to push out via IP address the same thing happens, it resolves to a totally different PC name, which is incorrect according to our DNS. It is like the SEPM servers have some kind of cached/out of date DNS. I have flushed DNS, rebooted multiple times, etc. Is there some kind of cached DNS happening on these servers?
Where is this hanging up at? This has never happened and is quite hindering to us suddenly. I basically can't push out managed clients to new/restaged PCs. I recently did a migration to a new SEPM server and get the same thing. Maybe this is because old/cached data came over from the original SEPM server?
Help! Thanks much --Kirk