Comments on: Another reason NOT to use a public DNS name as your internal domain namespace http://simultaneouspancakes.com/Lessons/2005/11/12/another-reason-not-to-use-a-public-dns-name-as-your-internal-domain-namespace/ Things I Wish I Had Known Mon, 06 Sep 2010 15:11:29 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: David Moisan http://simultaneouspancakes.com/Lessons/2005/11/12/another-reason-not-to-use-a-public-dns-name-as-your-internal-domain-namespace/comment-page-1/#comment-30 David Moisan Sun, 13 Nov 2005 04:09:19 +0000 http://simultaneouspancakes.com/Lessons/2005/11/12/another-reason-not-to-use-a-public-dns-name-as-your-internal-domain-namespace/#comment-30 I've seen this behaviour as well with the two SBS machines I'm responsible for (one at work, one personally owned.) I recently tried setting up a VPN client on one of the work XP systems to connect back to my home box. http://companyweb would resolve to the local (at work) SBS Sharepoint site rather than the remote site (my server), and pings verified this. IPCONFIG revealed some anomalous entries, notably a DNS server listed twice (e.g. under Primary DNS Server is listed "myserver.dom.loc myserver.dom.loc") This happened on all XP clients on the workplace SBS server. This did NOT happen, oddly enough, on my home XP box when connecting to the workplace VPN. (My home XP machine is connected to the home SBS box *but it is not joined to its domain*. Emphasis added, I think this may be an important fact.) We have two Macs at work but I haven't yet tried their VPN clients. I wonder what ifconfig would produce? When I'm next at work, I'll do some tests and post the results in my own blog (http://spaces.msn.com/dmoisan) I’ve seen this behaviour as well with the two SBS machines I’m responsible for (one at work, one personally owned.) I recently tried setting up a VPN client on one of the work XP systems to connect back to my home box.

http://companyweb would resolve to the local (at work) SBS Sharepoint site rather than the remote site (my server), and pings verified this.

IPCONFIG revealed some anomalous entries, notably a DNS server listed twice (e.g. under Primary DNS Server is listed “myserver.dom.loc myserver.dom.loc”)

This happened on all XP clients on the workplace SBS server. This did NOT happen, oddly enough, on my home XP box when connecting to the workplace VPN. (My home XP machine is connected to the home SBS box *but it is not joined to its domain*. Emphasis added, I think this may be an important fact.)

We have two Macs at work but I haven’t yet tried their VPN clients. I wonder what ifconfig would produce?

When I’m next at work, I’ll do some tests and post the results in my own blog (http://spaces.msn.com/dmoisan)

]]>