It happened again.
Somehow the DNS of my SBS 2011 adds a record in the Forward Lookup Zone of my local domains with 192.168.1.27. Unfortunatly this one has exactly the same name as my server and there is already an entry for my server 192.168.1.1.
As I run an SQL Server on this SBS, too, the clients now sometimes don't resolve the address correctly. Instead of getting IP of my server's original URL (used in the connect string to the SQL Server) as 192.168.1.1 they get (partially) the IP address 192.168.1.27. I can see it with PING <servername> /4 in the command prompt. But on this address my SQL server won't listen.
Resolution we found last time here was: delete this obsolete and unnecessary ghost record and reload the DNS and flush the DNS cach on the faulty client (IPCONFIG /FLUSHDNS). After that the server resolves correctly to 192.168.1.1 until the next ghost record
with the same IP address is added again.
I suspect this record is created as soon as somebody connects to the SBS by a remote connection/VPN.
Why is this record created and how can I stop this behavior? Or any other solution?
TIA
Henry