Well let's see... My .com is out in the cloud of the Internet, I don't externally expose DNS, and until you convince the SBS dev team, it's a moot point. In the mean time every time a SBS box says "gee I can't get to my externally hosted web site" we'll know that someone screwed up and didn't read the recommendations, understand why they were chosen. The reality is when you are licensed for Exchange, you are licensed for Outlook 2003. SBS owners are not suffering in the choice of .local. Sorry but my Postmaster@blah is a blah.com. As I said, every consultant has a fidiciary responsibility to their clients to ensure that any member of the SBS podcast can recognize that SBS box. Set up your own boxes in whatever manner you see fit, but when you are hired by a business owner, you have that responsibility to him. We have a full on Exchange/Outlook, I can use a cellphone to activesync to my firm emails, I can IMAP and POP and Outlook over Http, you've yet to convince me that I've lost anything in picking .com which means I now have to hack up my internal records to fix the fact that I can't get to a firm web site and document these changes from the typical SBS box so that when/if I get hit by a bus the next guy coming in the office can figure out what I did. Don't convince me. Convince the Dev team, until then in my mind it's just introducing complexity, not reducing it. I find it funny though that the 'religious wars' are over computer naming. I guess we should look at the bright side that we're advancing in our categories of disagreements :-)