Re: DNS issues on multi-homed DC's

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi
Why don't you let your FW decide (by configuring) who pass the WAN link to
the other side, instead of placing Multihomed DCs?

In this scenario, network adapters on the multihomed domain controllers are
registering both the inside and outside Internet Protocol (IP) addresses
with the DNS server. DNS name resolution lookup requests return records in a
"round robin" fashion, alternating the internal and external IP addresses.
Replication operations require multiple lookup requests of SRV records. In
this case, half of the DNS lookup requests return an IP address that cannot
be contacted, and the replication operation fails.
http://support.microsoft.com/kb/272294
--
===================================
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
===================================

"Josh Webster" <JoshWebster@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9E0E97F4-8527-487C-8138-5EEE0B7EC2D6@xxxxxxxxxxxxxxxx
I've got a question about whether or not the scenario I'm looking at is
possible.

I would have a child domain with locations at several different sites.
Each
site would have a DC, and each DC would reside on two networks, LAN and
WAN.
LAN side of each of the DC's would be in the same network range as each
other, and the DC's at each site would actually have the same IP address
on
the LAN adapter. WAN side, each DC would have a unique IP and routing
between
sites would be setup so that the DC's can replicate between each other.

The main issue I can potentially see here is with DNS. With AD integrated
DNS, each of the sites computer will have entries, and those entries would
normally be replicated between DC's. Am I missing a way to configure this
so
that DNS wouldn't be an issue? Any other issues that I've completely
overlooked in this setup? Any reason this would possible or not, and
whether
it would be recommended or not?

Thanks,
Josh


.

Relevant Pages

  • Re: Connect a Wireless Router to my SBS Network
    ... Here is my wireless configuration. ... WAN Type: Static IP Address ... Secondary DNS. ... Ethernet adapter Wireless Network: ...
    (microsoft.public.windows.server.sbs)
  • Re: Help with initial small org AD setup convention when using DMZ network
    ... Consider using Dynamic DNS internally (aka Active Directory Integrated ... > firewall which then connects the public IP dmz network to a private IP ... > domain name for such subnets based on the nearest airport code, ... > servers to serve acme.com names for external users. ...
    (microsoft.public.win2000.active_directory)
  • Re: About DNS naming convention for Active Directory
    ... Here's what I did so far, I set up a private network consists of the ... I did an in-place upgrade of the NT4 PDC to Active Directory 2003, ... I had no DNS service at all. ... Joined the 2003 Server as a member server and that went well too. ...
    (microsoft.public.windows.server.dns)
  • Re: IE cant connect to any sites
    ... On the General tab in the Temporary Internet Files Folder, ... Click on "LAN Settings" and make sure everything is blank, ... Network settings ... IP address automatically", click on the DNS tab, disable DNS here, click ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: Error Message
    ... On the General tab in the Temporary Internet Files Folder, ... Click on "LAN Settings" and make sure everything is blank, ... Network settings ... IP address automatically", click on the DNS tab, disable DNS here, click ...
    (microsoft.public.windows.inetexplorer.ie6.browser)