Agreed, people are dull. As I understand, MS recommended using corp.com domain, (perhaps as an example), which dull people then use. Any sane person would use ".local". I've seen that sort of junk before, when a server inside a FW would declare itself as the organization's public domain for the propose of sending email internally. Which ends up wrapping that whole network around the axle. Changing the domain is not a cakewalk from what I recall.