Re: DNS over NAT on separate subnets
- From: "Doug Sherman [MVP]" <dsherman@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 9 Mar 2006 13:46:48 -0500
Maybe a Site to Site VPN between the DCs.
Doug Sherman
MCSE, MCSA, MCP+I, MVP
"ablack@xxxxxxxxxxx" <ablackcarneyscom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:72E6225C-EE3B-45D8-B35A-AF1851EB883B@xxxxxxxxxxxxxxxx
I don't believe that this is possible, but I thought I would check. The206.15.87.x
scenario is this.
Subnet 1 206.15.87.x/24 Multiple W2K3 AD domain controllers and other
windows boxes. All work correctly and ultimately NAT via Cisco ASA to
internet (no problems at this site all OK DNS stable)
Subnet 2 connected over wireless radio to the inside of network
not through outside internet line our over Cisco ASA. This site has IP's1
11.50.200.x/24 and is NAT'd for security reasons to 206.15.87.10. with
another Cisco ASA at subnet 2 site. This segment can browse all of
206.15.87.x network and can hit internet via the NAT'd Cisco ASA at subnet
it
The problem I want to add a W2K3 domain controller at subnet 2 If I do,
will report it's DNS as 11.50.200.200 since this is its actual IP. Thiswill
work for subnet 2, but will cause problems at subnet 1 since this subnetaddress.
knows nothing about the 11.50.200.x network. If I change the DNS entry for
the server at subnet 2, then subnet 1 will be able to find the server, but
clients at subnet 2 will fail, since the address is the outsid NAT'd
Really don't know how to get around this, or if I should even try!
.
- Prev by Date: Re: How to Identify a culprit machine
- Next by Date: smb logging
- Previous by thread: Re: How to Identify a culprit machine
- Next by thread: Re: DNS over NAT on separate subnets
- Index(es):
Relevant Pages
|