AD DNS naming

Hi,

I have a problem I believe this group can help me with, in regard to AD
DNS naming. Thing is, I don't have an immediate problem which anyone needs
to work on, it is more that I am after opinions, discussion, and, well,
argument (in the proper sense of the word, not screaming matches).

My name's Mick Malloy and as you may guess from my moniker I'm an SBS
(Small Business Server) MVP. I became an MVP through involvement in
newsgroups and that is what has led me here. In search of an answer to my
question I've gone a fair way back into previous posts and 'lurked' for the
last few days, but really I find little discussion about my point of
interest.

My interest is discussion of the pros and cons of naming your AD DNS
..local vs a name related to your FQDN. I'm using .local here as a bit of a
generalisation, I actually prefer .lan due to the special handling some OS's
(OSX and a couple of Linux variants) use for the .local domain but if we
discount special handling or start from a premise of .whatever (as long as
it is not related to your internet FQDN) you are likely to understand where
I'm coming from.

/cards on the table time

I believe it is wrong to name your AD DNS with any relationship to your
internet FQDN. It is wrong to name your AD DNS company.com and it is only
slightly less wrong to name it branch.company.com.
I believe most people approach the question from the wrong angle, 'I
have this name (FQDN), I think I'll use it for my AD DNS.' where I believe
they should rather ask 'I need to create an AD DNS name, is there any reason
why it should relate to my public FQDN or should I use a different
namespace?'.

Pointers to previous discussion will be appreciated, and read.
Your participation in new discussion will be greatly appreciated.

TIA
MM


.

Relevant Pages

  • Re: How is .local Used?
    ... have a good understanding of the relationship between the AD and FQDN ... namespace definitions and the implications associated with their setup. ... DNS for internal delivery using the .local namespace. ... > servers, workstations) should look to an AD integrated DNS ...
    (microsoft.public.windows.server.sbs)
  • Re: reverse dns
    ... Our exchange server FQDN is abc.com ... I don't know how many problems this may cause, most DNS clients will ... Also set up maximum logging for your SMTP virtual server, ...
    (microsoft.public.windows.server.sbs)
  • Re: AD DNS naming
    ... Naming your AD domain in relationship to your FQDN guarantees that your ... I'm asking myself if I truly want to open my full AD DNS to another system, ... Internet servers will not resolve a .local name. ... I'll give it my FQDN', not having first thought about why. ...
    (microsoft.public.windows.server.dns)
  • =?Utf-8?Q?Re:_LDAP_Name_der_Active_Directo?= =?Utf-8?Q?ry_hat_sich_ver=C3=A4ndert?=
    ... Das DNS ist unabhängig vom AD und muss" korrekt funktionieren. ... In deinem genannten Beispiel "INTRANET" ist das ja das erste DNS-Label in ... deinem FQDN. ... Netz-Laufwerk verbinden. ...
    (microsoft.public.de.german.windows.server.active_directory)
  • Re: mail confusion
    ... >> For local networks, DNS is utterly and completely unnecessary, and so ... DNS works fantastically well for the Internet, ... a FQDN, even if most every site uses their FQDN as their DN. ...
    (Fedora)