DNS problem and Exchange 2000

[Robert W]

Hi all,

I have a nagging issue that may need some clarity from the group. First
paragraph will explain the environment and the second paragraph will detail
the problem.

Setup:
Exchange2K SP3 running on Windows2K SP4 Member server. This server will be
referred to as EX1. I have installed ESM on both DC servers, herein referred
to as DC1 and DC2. Both DC's have the same configuration as far as running
ESM with SP3 and SP 4 for Windows.

Problem:

When DC1 is manually restarted, EX1 is unable to function on the backup,
DC2. DC2 is a global catalog (GC) server. Here is where I believe the
problem starts, but need a nudge in the positive direction. DC1 is our
primary internal DNS server. We use an ISP DNS server as a forwarder and
HTTP lookup. DC2 does not currently have a forward lookup zone on it. DNS
is installed but not configured. Due to prior events a year ago, the DNS
configuration on DC1 had to be overhauled and is currently working in
"Standard Primary mode". I have a good feeling that when the DNS goes down,
so does Exchange. However, the last time I tried to configure DNS on DC2 and
do a test "switch-over" to have Exchange run off of DC2, EX1 still would not
locate the operational DC2.

So what I am wondering is the sequence in which to proceed. I need the
backup DNS or not? If yes, should I reconfigure the Standard Primary Zone to
an AD-Integrated Zone? After I do that, what are the steps for creating
that backup DNS server and is there a way that the backup, DC2 can just
maintain the copy of the DC1 DNS information so that should a downing of DC1
occur during business or overnight hours, EX1 will continue to function
without a hiccup?

TIA,

Robert W.

 

[Edward \(MSFT\)]

Robert,

If you setup DC1 to have Active Directory Integrated DNS, then setup the
forward lookup zone on DC2, then replication should take care of the
information on both DCs being seen on the other.

If DC1 continues to have Primary DNS zone and you setup a Secondary zone on
DC2 then you will have to rely on DNS zone transfers to replicate the
information from DC1 to DC2 as Primary zones are "writeable" but Secondary
zones would be just a copy of what was on DC1.

If you setup DC1 with AD integrated, make sure you are replicating fine
between DC1 and DC2. Make sure that all the SRV records, etc. are in the
forward lookup zone of your domain.

You can set EX1 to have a "preferred" DNS of DC1 and an "alternate" DNS of
DC2 after this is setup.

Remember that "forwarding" is only a "per server" setting and would need to
be setup for DC1 and DC2 should DC1 be unavailable for any given time.

--
Edward Dake
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Hi all,

I have a nagging issue that may need some clarity from the group. First
paragraph will explain the environment and the second paragraph will detail
the problem.

Setup:
Exchange2K SP3 running on Windows2K SP4 Member server. This server will be
referred to as EX1. I have installed ESM on both DC servers, herein referred
to as DC1 and DC2. Both DC's have the same configuration as far as running
ESM with SP3 and SP 4 for Windows.

Problem:

When DC1 is manually restarted, EX1 is unable to function on the backup,
DC2. DC2 is a global catalog (GC) server. Here is where I believe the
problem starts, but need a nudge in the positive direction. DC1 is our
primary internal DNS server. We use an ISP DNS server as a forwarder and
HTTP lookup. DC2 does not currently have a forward lookup zone on it. DNS
is installed but not configured. Due to prior events a year ago, the DNS
configuration on DC1 had to be overhauled and is currently working in
"Standard Primary mode". I have a good feeling that when the DNS goes down,
so does Exchange. However, the last time I tried to configure DNS on DC2 and
do a test "switch-over" to have Exchange run off of DC2, EX1 still would not
locate the operational DC2.

So what I am wondering is the sequence in which to proceed. I need the
backup DNS or not? If yes, should I reconfigure the Standard Primary Zone to
an AD-Integrated Zone? After I do that, what are the steps for creating
that backup DNS server and is there a way that the backup, DC2 can just
maintain the copy of the DC1 DNS information so that should a downing of DC1
occur during business or overnight hours, EX1 will continue to function
without a hiccup?

TIA,

Robert W.