"Why MS couldn't tell people from the get go to use .com instead of .local beats me" ..so now it's MS responsibility to help you design your network? What's really funny is that .local works just fine for 99.444% of the deployments that use them... ________________________________ From: isalist-bounce@xxxxxxxxxxxxx on behalf of Andrew English Sent: Wed 5/10/2006 8:37 AM To: isalist@xxxxxxxxxxxxx Subject: RE: [isalist] VPN issue Hi, I posted a issue a while ago that I as having when with this VPN connection were I'd get connected but couldn't resolve any of their servers via their names. I could access them via IP without any problems. Someone replied regarding External DNS and the rest I can't remember right now, anyhow the local DNS for this company is (SIGH) .local while the external is .com :( Why MS couldn't tell people from the get go to use .com instead of .local beats me, I am already dreading the thought of trying to deploy RPC over HTTP again. Regards, Andrew oops my bad with the first post! :) All mail to and from this domain is GFI-scanned.