| I haven't found it yet. I'm pretty sure the discussion against it was in | O'Reilly's "TCP/IP Network Administration". I've browsed through it in my
I've got that one and their DNS/BIND book at home - I'll glance through them tonight. | I had this problem at a place I consult for. They advertised everything | as domain.tld. When we needed to move the mail server elsewhere, we had a | couple thousand users to contact and have change their POP/IMAP/SMTP | settings. If it had been done right the first time, we'd have saved a few | weeks work. I don't think it's a good idea to advertise _everything_ as domain.tld; I just think it's wise for the convenience of your web site visitors and the id10ts out there to have domain.tld and www.domain.tld pointing to the same place, or have redirection set up on domain.tld to send the browser to www.domain.tld (Google's an example). I do always create records (even if they're often CNAMEs) for specific services, and advertise them separately. Here at my office, I've got webmail, mail, and smtp records (as well as other administrative hostnames) all pointing to the same box. If any one of those services becomes too burdonsome and needs to be offloaded, it can be done without much hassle. Our root domain and the www record point to a different box which primarily handles the website. Ftp services are on a separate machine, with a hostname to go with it. I was looking for a technical reason not to do it, not an administrative reason. I realize that there can be perils associated with it, but as long as you CNAME a hostname for each service from the beginning, there's not going to be a large number of users that use just domain.tld for those services. Steve ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
