1 domain 2 sites, what now?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I currently have 1 domain with two sites; previously I had just 1 site. The
new site has its own Domain Controller, and I would also like it to have its
own DNS server. I would like to know the best possible way to configure the
new DNS server taking into consideration that it is in a different site. If
anyone knows of a URL that explains the best practices for DNS setups, and
configuration for multiple sites I would be most grateful.

Cheers,
Sam
 
Sam said:
Hi,

I currently have 1 domain with two sites; previously I had just 1
site. The new site has its own Domain Controller, and I would also
like it to have its own DNS server. I would like to know the best
possible way to configure the new DNS server taking into
consideration that it is in a different site. If anyone knows of a
URL that explains the best practices for DNS setups, and
configuration for multiple sites I would be most grateful.

It can have its own DNS server, the zone will replicate from the current DC
if you use AD integrated zones.
825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;825036
 
Hi Kevin,

Thanks for the information. You probably don't remember me, but you were
very helpful to me a year ago when my DNS servers were not synchronizing due
to a SP4 error.

Thanks,
Sam
 
Hi,

I have installed DNS on the Site’s Domain Controller and setup a reverse
lookup zone for that subnet, and it is working fine, but I have some
questions on the forward lookup zone.
1.Should I create a new forward zone for this site?

2.Under the forward lookup zone site should this contain SRV records with
the new the new DNS server’s FQDN.

3.In event viewer I get the following error messages
Dynamic registration or deregistration of one or more DNS records failed
because no DNS servers are available.

The File Replication Service is having trouble enabling replication from DC1
to DC3 for c:\winnt\sysvol\domain using the DNS name DC1.WIND-GATE. FRS will
keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name DC1.WIND-GATE from this
computer.
[2] FRS is not running on DC1.WIND-GATE.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
 
Sam said:
Hi,

I have installed DNS on the Site's Domain Controller and setup a
reverse lookup zone for that subnet, and it is working fine, but I
have some questions on the forward lookup zone.
1.Should I create a new forward zone for this site?

No, do not create a new zone, the zone will replicate to this DC. You should
use netdiag and dcdiag to verify DNS registration and replication.
2.Under the forward lookup zone site should this contain SRV records
with the new the new DNS server's FQDN.

3.In event viewer I get the following error messages
Dynamic registration or deregistration of one or more DNS records
failed because no DNS servers are available.

Point the each DC to the other for preferred then to itself for alternate
DNS.
The File Replication Service is having trouble enabling replication
from DC1 to DC3 for c:\winnt\sysvol\domain using the DNS name
DC1.WIND-GATE. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name DC1.WIND-GATE from
this computer.
[2] FRS is not running on DC1.WIND-GATE.
[3] The topology information in the Active Directory for this
replica has not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the
problem is fixed you will see another event log message indicating
that the connection has been established.

Hmm, dc1.wind-gate? Is wind-gate the actual DNS domain name for your AD
domain?
If it is, that is a single-label domain name and it will cause 5781 events
starting with SP4 in Win2k and all XP and Win2k3. Make these registry fixes
on all your domain members.
300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684
 
Hi Kevin,

Thanks for the Info I will try and let you know how it turns out.

Best regards,
Sam

Kevin D. Goodknecht Sr. said:
Sam said:
Hi,

I have installed DNS on the Site's Domain Controller and setup a
reverse lookup zone for that subnet, and it is working fine, but I
have some questions on the forward lookup zone.
1.Should I create a new forward zone for this site?

No, do not create a new zone, the zone will replicate to this DC. You should
use netdiag and dcdiag to verify DNS registration and replication.
2.Under the forward lookup zone site should this contain SRV records
with the new the new DNS server's FQDN.

3.In event viewer I get the following error messages
Dynamic registration or deregistration of one or more DNS records
failed because no DNS servers are available.

Point the each DC to the other for preferred then to itself for alternate
DNS.
The File Replication Service is having trouble enabling replication
from DC1 to DC3 for c:\winnt\sysvol\domain using the DNS name
DC1.WIND-GATE. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name DC1.WIND-GATE from
this computer.
[2] FRS is not running on DC1.WIND-GATE.
[3] The topology information in the Active Directory for this
replica has not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the
problem is fixed you will see another event log message indicating
that the connection has been established.

Hmm, dc1.wind-gate? Is wind-gate the actual DNS domain name for your AD
domain?
If it is, that is a single-label domain name and it will cause 5781 events
starting with SP4 in Win2k and all XP and Win2k3. Make these registry fixes
on all your domain members.
300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684


--Â
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
 
Hi Kevin,

Thanks for the advice, everything is now good.

Regards,
Sam

Kevin D. Goodknecht Sr. said:
Sam said:
Hi,

I have installed DNS on the Site's Domain Controller and setup a
reverse lookup zone for that subnet, and it is working fine, but I
have some questions on the forward lookup zone.
1.Should I create a new forward zone for this site?

No, do not create a new zone, the zone will replicate to this DC. You should
use netdiag and dcdiag to verify DNS registration and replication.
2.Under the forward lookup zone site should this contain SRV records
with the new the new DNS server's FQDN.

3.In event viewer I get the following error messages
Dynamic registration or deregistration of one or more DNS records
failed because no DNS servers are available.

Point the each DC to the other for preferred then to itself for alternate
DNS.
The File Replication Service is having trouble enabling replication
from DC1 to DC3 for c:\winnt\sysvol\domain using the DNS name
DC1.WIND-GATE. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name DC1.WIND-GATE from
this computer.
[2] FRS is not running on DC1.WIND-GATE.
[3] The topology information in the Active Directory for this
replica has not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the
problem is fixed you will see another event log message indicating
that the connection has been established.

Hmm, dc1.wind-gate? Is wind-gate the actual DNS domain name for your AD
domain?
If it is, that is a single-label domain name and it will cause 5781 events
starting with SP4 in Win2k and all XP and Win2k3. Make these registry fixes
on all your domain members.
300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684


--Â
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
 
Back
Top