I have a few clients that VPN into are network. They use remote desktop to connect to their internal machines. I heard complaints they weren't able to connect using the compter name. For example "bill.contoso.com". I checked DNS and saw no record for their internal PC. The internal PC is connected to the domain and appears under the Computers container in AD. I went into DNS to look at the TTL perameters for contoso.com (Forward Lookup Zone).
Refresh Interval: 15mins
Retry Interval: 10 mins
Expires 1 day
Minimal TTL 1 hour
Were running MS Server 2003
I do not have problems on any other pc vpning in doing a remote desktop connection. The 2 machines that are having problems are Viesta machines. Any ideas?
Windows clients/servers will register themselves in DNS independent of it's configured with static IP or DHCP-lease. A requirement for dynamic DNS registration is that DHCP Client service is running as automatic on all machines and that the DNS-zone allows dynamic updates.