The official blog for Windows Server Essentials and Small Business Server support and product group communications.
[Today's post comes to us courtesy of Becky Ochs]
We’re getting some great questions here at the SMB Summit. One of yesterday’s geeky questions of the day was, "Why are we are defaulting to use .local as the DNS extension for Windows SBS 2008? Isn’t that a problem for Macs?"
So here’s our logic for using .local and why we still make it flexible for you to choose your own internal domain extension . . .
And for those of you SBS 2003 folks out there who use Macs, here's a quick plug for the whitepaper that discusses how to add a Mac to an SBS 2003 network:
Why make it so hard to use split-DNS?
It's very frustrating that we have to use an ansfer file to have this functionality.
Can you please explain why 'advanced configuration' is made more difficult to configure?
Is there a problem with split-DNS that you are trying to push people away from?
Shouldn't this have an SBS 2008 tag?
I still prefer the 'corp.example.com' naming convention over the 'example.local' convention. It makes dealing with split DNS a lot simpler and you get the benefit of DNS suffix search for single label lookups.
Still seeing lots of Exchange configs announcing a .local address in SMTP greetings, despite all those wizards.