Posted on 2007-12-05
Have a simple DNS server setup which is working fine. The problem is this:
When users are on our network they do not need to use the FQDN to resolve to a pc/server. E.G. they can connect to a server using server1 instead of server1.example.com. I used to think this was because the machine was added to the zone file on the DNS server so hence you did not have to specify the FQDN (I have DDNS setup so when the machine grabs an IP of the DHCP the DNS server gets updated with machines name) but I have tested this a little bit and even if the machine is using a static IP and not added to the DNS zone it can still resolve through server1 and not server1.example.com.
The problem I have is when people connect in via our VPN. If they connect via VPN using the same machine they now have to resolve using the FQDN. This works fine however it causes some issues as there are number of tools that they use which work of our servers... however these tools do not use the FQDN e.g they would just use server1 instead of server1.example.com. So when users connect via the VPN they cannot use these tools.
Is there any way of resolving this issue? I don't really understand DNS enough to know why when the client machine is on our network (even when its not resolving itself) it does not have to use the FQDN, however once connecting via the VPN it does.
Hope somebody can help.