RE: [Declude.JunkMail] [OT] .local domains
Just my .02: ".local" should not be used, and I hate using bogus TLD's. MS's suggestion (and a valid RFC suggestion) is to use a sub-domain of your current domain. So if your company domain (for email/web/etc) is: company.com, you could use: hq.company.com. It is RFC compliant, will not interfere with your Internet presence domain name, and works well. Stan Lyzak BSEE, CISSP, MCSE², CCNA, Security+, A+ Network Security Engineer ASysTech, Inc. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of R. Scott Perry Sent: Wednesday, September 01, 2004 5:17 PM To: [EMAIL PROTECTED] Subject: Re: [Declude.JunkMail] [OT] .local domains >As I was lurking on this list I noticed a thread "Question about >Exchange2Aliases" where .local was suggested as an example TLD. .local should not be used. RFC2606 specifies that aside from TLDs that have already been allocated (.com, .net, .museum, .info, .uk, etc.), it is also OK to use .test, .example, .invalid, and .localhost. Also, example.com/example.net/example.org are OK to use. >If you have Mac OS X boxes on your network and you want to have them as >members of a Microsoft Active Directory Domain then you cannot use >.local as this extension is used by some OS X service (Rendezvous >discovery service I believe). The TLD ".lan" seems to work and also >connotes a "local" area network. We use .lan for our local DNS >services required for Active Directory. This allows us to manage our >local DNS zone "commarts.lan" >without affecting our internet DNS records (on our ISP's DNS servers). FYI, both ".local" and ".lan" are invalid (and could cause problems now or in the future). If they leak (appearing in E-mail headers, for example), there could be problems. Or, if a TLD you choose becomes allocated in the future, you're going to encounter big problems. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000. Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection. Find out what you've been missing: Ask for a free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] [OT] .local domains
Scott, Thanks for the additional info. When we first implemented MS Active Directory we used .local (because most documentation on Active Directory suggested .local as an example TLD). Changing Domain names in MS Active Directory is no trivial matter even in a small domain. If I could start from scratch again ".localhost" it would be. But for now ".lan" will have to do until it is allocated in the future. Again, thank you for the list of allowed TLD's. Michael Hoyt Communication Arts 110 Constitution Drive Menlo Park, CA 94025 (650) 326-6040 fax:(650) 326-1648 e-mail: [EMAIL PROTECTED] Web Site: http://www.commarts.com --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
Re: [Declude.JunkMail] [OT] .local domains
As I was lurking on this list I noticed a thread "Question about Exchange2Aliases" where .local was suggested as an example TLD. .local should not be used. RFC2606 specifies that aside from TLDs that have already been allocated (.com, .net, .museum, .info, .uk, etc.), it is also OK to use .test, .example, .invalid, and .localhost. Also, example.com/example.net/example.org are OK to use. If you have Mac OS X boxes on your network and you want to have them as members of a Microsoft Active Directory Domain then you cannot use .local as this extension is used by some OS X service (Rendezvous discovery service I believe). The TLD ".lan" seems to work and also connotes a "local" area network. We use .lan for our local DNS services required for Active Directory. This allows us to manage our local DNS zone "commarts.lan" without affecting our internet DNS records (on our ISP's DNS servers). FYI, both ".local" and ".lan" are invalid (and could cause problems now or in the future). If they leak (appearing in E-mail headers, for example), there could be problems. Or, if a TLD you choose becomes allocated in the future, you're going to encounter big problems. -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000. Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection. Find out what you've been missing: Ask for a free 30-day evaluation. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
[Declude.JunkMail] [OT] .local domains
As I was lurking on this list I noticed a thread "Question about Exchange2Aliases" where .local was suggested as an example TLD. If you have Mac OS X boxes on your network and you want to have them as members of a Microsoft Active Directory Domain then you cannot use .local as this extension is used by some OS X service (Rendezvous discovery service I believe). The TLD ".lan" seems to work and also connotes a "local" area network. We use .lan for our local DNS services required for Active Directory. This allows us to manage our local DNS zone "commarts.lan" without affecting our internet DNS records (on our ISP's DNS servers). Also if anyone out there is attempting to join Mac OS X computers to a Microsoft Active Directory Domain then check out ADMitMac from www.thursby.com - it works well in our small office environment and is worth the $ if you do not have the time to figure out the ins and outs of Active Directory (which didn't work in the early releases of OS X but may work fine now). Michael Hoyt Communication Arts 110 Constitution Drive Menlo Park, CA 94025 (650) 326-6040 fax:(650) 326-1648 e-mail: [EMAIL PROTECTED] Web Site: http://www.commarts.com --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
