GPO for TCP/IP settings?

[MandG]

Is there some way to create a GPO that will configure all domain
computers to register their TCP/IP settings on the DNS server?

I'm trying to figure out how to set up Host (A) records for all of the
clients and with the least amount of effort.

Thanks.

 

[Enkidu]

Is there some way to create a GPO that will configure all domain
computers to register their TCP/IP settings on the DNS server?

I'm trying to figure out how to set up Host (A) records for all of the
clients and with the least amount of effort.

Why do you need a GPO? One would have thought that you were using DHCP
and you can configure DHCP to update DNS when a machine gets an IP
address. Or am I missing something?

Cheers,

Cliff

 

[MandG]

Why do you need a GPO? One would have thought that you were using DHCP
and you can configure DHCP to update DNS when a machine gets an IP
address. Or am I missing something?

Thanks Cliff- I looked into the DHCP configuration and am now more
confused... The DNS properties for this DHCP scope are in fact set to
"Automatically update DHCP client information in DNS".

However, we have 2 DNS servers - one on this AD domain controller and
one that's running DNS only. I looked at the Forward Lookup Zones on
both of these and they each have differnet Host records. But still,
neither of them had *all* of the clients that are on the domain.

So, now,

1) I don't which DNS server the client are updated to

2) I don't know why neither one of the DNS servers contains *all* Host
records and instead contain only some.

3) I don't know why the two DNS servers aren't replicating

 

[Enkidu]

Thanks Cliff- I looked into the DHCP configuration and am now more
confused... The DNS properties for this DHCP scope are in fact set to
"Automatically update DHCP client information in DNS".

However, we have 2 DNS servers - one on this AD domain controller and
one that's running DNS only. I looked at the Forward Lookup Zones on
both of these and they each have differnet Host records. But still,
neither of them had *all* of the clients that are on the domain.

So, now,

1) I don't which DNS server the client are updated to

2) I don't know why neither one of the DNS servers contains *all* Host
records and instead contain only some.

3) I don't know why the two DNS servers aren't replicating

Number 3 is the crucial one. If the DNS is integrated then it doesn't
matter which one gets updated and both DNS servers should be in line.

Cheers,

Cliff

 

[Jorge de Almeida Pinto [MVP - DS]]

either you have:
* both servers hosting AD-intergrated DNS zones (DNS installed on a DC makes
this possible and is preferred!)
* one server hosting a primary DNS zone and the other a secondary DNS zone

if you have twp primaries, then those servers will not share information
with each other

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx

 

[MandG]

if you have twp primaries, then those servers will not share information
with each other

ok, thanks guys- Now for the stupid question. Where do I determine if
the non-AD DNS server was configured as a Primary or Secondary?

 

[Ace Fekay [MVP]]

In

ok, thanks guys- Now for the stupid question. Where do I determine if
the non-AD DNS server was configured as a Primary or Secondary?

Look at the non-DC DNS server's DNS console, zone properties, it will state
a Master IP it is receiving zone transfers from. If not, it's a Primary.

Ace

 

[MandG]

In

Look at the non-DC DNS server's DNS console, zone properties, it will state
a Master IP it is receiving zone transfers from. If not, it's a Primary.

Ace

OK, thanks. Looks like I have 2 Primary's - one AD integrated and the
other just simply Primary. So, I can see now that neither were set up
for zone transfers - I'll just manually recreate the records on the AD
server from the simple Primary server and eventually reinstall the
Primary as a Secondary.

Thanks all for your help -

 

[Ace Fekay [MVP]]

In

OK, thanks. Looks like I have 2 Primary's - one AD integrated and the
other just simply Primary. So, I can see now that neither were set up
for zone transfers - I'll just manually recreate the records on the AD
server from the simple Primary server and eventually reinstall the
Primary as a Secondary.

Thanks all for your help -

A "Primary" AD Integrated zone is misleading. Basically, AD Integrated zones
are act as a Primary, but the differences is the data is stored in the AD
database and already exists on all DC (dependin on the replication scope
settings). If the zone is already AD integrated, just install DNS on the
other DC and the zone will automatically show up.

Ace

 

[MandG]

A "Primary" AD Integrated zone is misleading. Basically, AD Integrated zones
are act as a Primary, but the differences is the data is stored in the AD
database and already exists on all DC (dependin on the replication scope
settings). If the zone is already AD integrated, just install DNS on the
other DC and the zone will automatically show up.

Ace

Can't replicate through AD since we're only running a single DC. I
hope to change this soon though and configure another DC server with
DNS.

Thanks again.

 

[Ace Fekay [MVP]]

In

Can't replicate through AD since we're only running a single DC. I
hope to change this soon though and configure another DC server with
DNS.

Thanks again.

AD Integrated zones act like a Primary zone so they are capable of allowing
zone transfer to a Secondary too.

Ace