The MS example I saw was to use a domain that ended .local if you did not want to use a real/public domain.  This seems to work, let’s hope that .local never becomes a real tld.

 

Sincerely,

 

Jonathan Miller

Internet Service Department

ACCS.net

Advanced Computer & Communication Systems, Inc.


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Bramble
Sent: Monday, September 22, 2003 2:05 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] VeriSteal is stealing traffic from your domain.

 

This AD server is over 2 years old.  Support was very weak back then.  It was set up as a trial of AD so I could see if there was any benefit to using it on my production server.  I decided that is was not useful and too many problems existed.

I do see the reasoning in either owning the domain or using a fake TLD.  Eventually the fake TLDs though could come back and haunt users if they are ever allowed to be registered for Internet use.  I believe that will happen some day.

Matt



Joshua Levitsky wrote:



On Sep 22, 2003, at 1:40 PM, Matthew Bramble wrote:

Who says that I have to register the domain that Active Directory is using?  My Active Directory name isn't intended to be used on the Internet.  In most installations, you look to your own Active Directory server first for the lookups, so if it exists on the Internet it won't interfeer...until now.


In my MCSE class the Microsoft printed material said to use ".local" if you didn't have an internet domain. I always do it that way when the company I do consulting for doesn't have a domain or if they have a domain and the mail / web is at a hosting company. If the domain isn't totally in-house then I use .local

-Josh

 

Reply via email to