Re: DHCP keeping host names unique

Actually, that was one of the issues I've been trying to tease out of
all that documentation. If a desktop has the check box set on the DNS
tab of IP properties for it to register the desktop with DNS then I
believe that DHCP server could literally register each name in some
central dns-domain. Say the central domain is central.local, and the
DHCP server would check each host (preferably netbios name) to ensure
that the host has a unique name and IP address.

Then have the host login with it's primary domain, say AD1.biz.com.
That login process would apply GPO s to assign primary domain name,
AD1.biz.com, a list of search suffixs, say AD2.biz.com ( a different AD
forest same company, we have more than two AD forests), fin.AD1.biz.com
(subdomain), update WINS server search list, update name server search
list. I believe you can do all this with GPO?

I believe that the end result would be that each host would update it's
own DDNS with it's assigned primary AD DNS. The central DHCP server
would ensure unique names, All hosts are ensured to be in WINS.

We've had problems where someone has a server registered not by it's
netbios name but some other name in DNS in the other AD forest. Then
when another server administrator properly assigns that other domains
server, netbios name as a DNS entry, WINS will see one, DNS will see
the other, and depending upon which domain the desktop is assign to and
if it has a suffix search list or not, the target name may or may not
be seen.

I'd like to run a central dns/dhcp server to get a flat host name out
there, have the AD DDNS update itself from the login process. Then
have AD DNS domain use my central dns as a secondary name server, if
they're not paranoid about the resources being 'available' on the
central dns . If they are cautious, I'll forward the queries to their
DNS and they may apply their own ACLs. Have all the AD DNS servers
load the central (or buisness) zone, it's just host names. ( security
is in the authentication process, right) Have each host of AD point to
it's own DNS. It'll see at one server the host names available. Other
domain's resources will be available through trusts and privledges.

Or did I interpret your answere correctly

Herb Martin wrote:
> "mmccaws2" <mmccaws@xxxxxxxxxxx> wrote in message
> news:1137774853.362525.66080@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Because of Exchange and it's WINS dependancy is it possible of setting
> > the DHCP server to only provide addresses to hosts with unique netbios
> > names. WINS is a flat file system that does not understand subdomains.
> > So the objective is to ensure that the host names are unique. However
> > there are multiple domains. Is there a setting to test the uniqueness
> > of the host name?
>
> No. Not unless you can isolate the clients to different
> subnets and thereby to different scopes and perhaps even
> different DHCP servers.
>
> If the machines are all set to properly use their DNS-domain
> name (in the SYSTEM CONTROL panel), which they should
> be, then you can have the clients register themselves rather
> than the DHCP server do it.
>
> Start with getting the domain name correct on each machine
> (preferable AS it joins the domain but do it now if you must.)
>
> Usually the check box that have the name "follow" or "change"
> when the domain is changed should be checked to do that.
> (So if a machine leaves one domain and joins another the
> full name changes automatically whether you remember or not.)
>
> Also note that this is important to get right in the SYSTEM
> CONTROL panel (and that the NIC suffixes settings are not
> nearly as critical or useful on getting this right.)
>
> --
> Herb Martin, MCSE, MVP
> Accelerated MCSE
> http://www.LearnQuick.Com
> [phone number on web site]

.

Relevant Pages

  • Re: Tracing emails from outside clients
    ... Wherever you wish to host the DNS just make sure you create the identical ... The secondary server arrangement is just a legacy thing. ...
    (microsoft.public.exchange.misc)
  • Re: Web Site Mystery
    ... host our own web site at this location. ... So in our DNS setup, there is a pointer to the ip address of the ... Run an ipconfig /all on your server and you'll see the ... www.europacrown.com don't work from our corporate network. ...
    (microsoft.public.windows.server.general)
  • Re: Web Site Mystery
    ... host our own web site at this location. ... So in our DNS setup, there is a pointer to the ip address of the ... Run an ipconfig /all on your server and you'll see ... www.europacrown.com don't work from our corporate network. ...
    (microsoft.public.windows.server.general)
  • Re: How to disable the "implicit mx record" in Exchange
    ... the host with the A record for the actual domain. ... So when Exchange gets a DNS timeout looking up an MX record, ... their own Exchange or other type of mail server under their own domain name, ... DNS UDP traffic max packet size is ...
    (microsoft.public.exchange.admin)
  • Re: How to disable the "implicit mx record" in Exchange
    ... the host with the A record for the actual domain. ... So when Exchange gets a DNS timeout looking up an MX record, ... our ISP's DNS and perhaps slow response from the recipient domain's ... their own Exchange or other type of mail server under their own domain name, ...
    (microsoft.public.exchange.admin)