GPIA7R wrote: »
So, one of our genius remote techs apparently put a PC in the Computers OU in AD. They NAMED the PC the IP of our DNS server. The hell?
Oddly, now we can't trace it. Obviously can't ping or tracert the PC because we'd just get the results from our DNS.
Any thoughts on this? Are there any ways to specify that I'm looking for a hostname when I input an actual IP?
If it's a host joined to the domain, couldn't you ping <name that is an IP address>.<domain> and get the actual IP?
For example if the hostname is "220.127.116.11" and your domain is "company.com," can't you ping or tracert "18.104.22.168.company.com?"
This may be more problematic if the OSX box is a remote host, depending upon your VPN implementation.
You can try pinging the fully qualified domain name of the PC. If the PC is named 192.168.0.1 and your AD domain is contoso.com it would be 192.168.0.1.contoso.com. A more normal name would be accounting05.contoso.com. Otherwise Djeet is on the right track, check the DHCP leases.
edit: oops reading comprehension, already suggested