I have a dictation server statically assigned to 192.168.0.201. I have two clients who routinely connect to this with dictation clients.
I virtualized the server last week to do some testing and though I thought I had isolated the VM from the network when I booted it up, I'm guessing the virtual machine got on the network and grabbed an IP number of 192.168.0.34. Upon noticing this I turned the VM off. The physical server is still running live and I have had the VM off ever since.
However, when I look at my DNS server the A record for the dictation server is set at 192.168.0.34. My dictation clients are getting updates from this DNS server and trying to connect to the wrong IP (.34) where there is no computer. I manually
change the DNS entry in AD back to .201, run ipconfig /flushdns on my clients and they connect fine to .201 for the rest of the day. But the next day when I come back in to the office the A record has been set back to .34 and the clients cannot connect
again. I have three DNS servers in my domain. How can I find out where these incorrect updates are coming from?