architecture question

[Jeremy P]

I understand letter of the law, spirit of the law and playing it safe to
avoid headaches.

However, there are times where registering a real domain just isn't
practical.  For example, I'm not going to ask all of the students in my
courses to go out and register a .com for the semester.  It would be a
waste of money as their systems never leave the local network, except
through a NAT connection.  So in those types of instances, I'm assuming
.lan or .test are safest?


On Wed, May 8, 2013 at 11:20 AM, Steven Carr <sjcarr at gmail.com> wrote:

> On 8 May 2013 18:09,  <WBrown at e1b.org> wrote:
> > This just came up with a site I support.  Thanks to this list and the
> > DNS-OARC list, I know better. Hopefully, I can redirect them to use
> > something below their real domain for Active Directory such as
> > ad.example.org.
>
> FWIW: MS now advises not to use .local for internal AD anymore. They
> suggest you use your owned/registered namespace to prevent domain
> collisions.
>
> http://support.microsoft.com/kb/909264
> Generally, we recommend that you register DNS names for internal and
> external namespaces with an Internet registrar... Registering your DNS
> name with an Internet registrar may help prevent a name collision.
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20130508/dca62698/attachment.html>