DNS registers real IP rather than NAT IP address

[Walter Moore]

Hi all,

Here's the situation. My client PC's are on a 132.X.X.X network. My Win2K
Domain Controllers and DNS are on a 204.X.X.X network. There is NAT in
between the PC's and the DNS. There are some dopey reasons for this
configuration which I don't care to go into.

The Client's NAT to a 204.X.X.X address. A static route has been added so
the NAT addresses can make it back home.

The issue is that my DNS, which is dynamic, records the 132.X.X.X address of
the clients rather than their 204.X.X.X address. Because of this, I am
unable to take advantage of some advanced Win2K AD functions.

All of my clients can log in just fine and map to shares with no difficulty.
But I cannot manage workstations from the domain controllers because name
resolution is wrong.

Aside from assigning everyone in the organization a static IP and manually
mapping the NAT'd addresses to the clients, is there some other solution?

Any information you can provide will be greatly appreciated!

 

[Michael]

I guess someday when I have nothing better to do I would
like to here your configuration reason.
I take it you are running AD, is there a firewall some
where on this network? Are you connecting the two subnets
by WAN or LAN?
Michael

 

[Jonathan de Boyne Pollard]

WM> The issue is that my DNS, which is dynamic, records the
WM> 132.X.X.X address of the clients rather than their 204.X.X.X
WM> address.

As it should. Those are the IP addresses that those machines have, and those
are thus the IP addresses that the DHCP clients on those machines will
register with your content DNS server. The machines don't actually _have_
204.*.*.* IP addresses.

Get rid of the NAT, and correct your routing so that the 132.*.*.* and
204.*.*.* networks can intercommunicate properly. If the 132.*.*.* network is
hiding behind NAT because of an address space conflict between that and
Internet, then now is the time to read RFC 1918 and fix that, too.