Do clients need to register in DNS?

[mismomma]

We have not yet implemented AD - I am currently in the end
of design phase.

Do I need to do dynamic registration of clients? I am
allowing the servers to dynamically register.

We are running BIND DNS throughout now (it holds x.com -
for example). With AD implementation, our current design
is:

- Empty root (ad.x.com) with 2 subdomains (a.ad.x.com and
b.ad.x.com)
- BIND v9 server is now in every geographic location
- Planning on a Single Zone (for all 3 domains) and
running DDNS on W2K empty root servers.
- Place the root server in each geographic location (where
the BIND servers are)
- All locations are connected by T1 or more
- BIND holds a secondary of ad.x.com
- Clients still point to BIND for primary DNS
- W2K DDNS servers forward to BIND
- DHCP also runs on the BIND servers and it registers the
clients as cleintname.DHCP.x.com on the BIND DNS servers
- W2K DDNS servers do not register client names

What would I be loosing in AD by not registering the
clients on the W2K side as clientname.a.ad.x.com

If you have any comments on this design - please assist.

 

[Ace Fekay [MVP]]

In

We have not yet implemented AD - I am currently in the end
of design phase.

Do I need to do dynamic registration of clients? I am
allowing the servers to dynamically register.

We are running BIND DNS throughout now (it holds x.com -
for example). With AD implementation, our current design
is:

- Empty root (ad.x.com) with 2 subdomains (a.ad.x.com and
b.ad.x.com)
- BIND v9 server is now in every geographic location
- Planning on a Single Zone (for all 3 domains) and
running DDNS on W2K empty root servers.
- Place the root server in each geographic location (where
the BIND servers are)
- All locations are connected by T1 or more
- BIND holds a secondary of ad.x.com
- Clients still point to BIND for primary DNS
- W2K DDNS servers forward to BIND
- DHCP also runs on the BIND servers and it registers the
clients as cleintname.DHCP.x.com on the BIND DNS servers
- W2K DDNS servers do not register client names

What would I be loosing in AD by not registering the
clients on the W2K side as clientname.a.ad.x.com

If you have any comments on this design - please assist.

It depends on your requirements. Some companies don't allow registration of
clients. FOr example, a local well known university does not allow it since
there are many changes constantly, users logged on only for a short time,
laptops, wireless, etc, just too much "junk".

It would also depend on what apps you are using and if they require that a
host has an FQDN entry.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[mismomma]

I was looking for more detail on the limitations of not
having clients names in the ad zone - no FQDN. At this
time we do not have any apps that require a FQDN in AD
because we are not using AD. However, I am trying to plan
this for the future, so what apps or types of apps might
require a fqdn. Is this a major concern or are there
usually other workarounds to use those apps?

 

[Ace Fekay [MVP]]

In

I was looking for more detail on the limitations of not
having clients names in the ad zone - no FQDN. At this
time we do not have any apps that require a FQDN in AD
because we are not using AD. However, I am trying to plan
this for the future, so what apps or types of apps might
require a fqdn. Is this a major concern or are there
usually other workarounds to use those apps?

Honestly I can't think of any off hand. I had a list awhile ago, but can't
find it. You would have to check with your vendor(s) if they require this
functionality. I know some Unix apps require a reverse zone, if that helps.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory