NAT routing DNS trouble with Server 2008
greetings,
i’ve upgraded server 2003 standard server 2008 r2 standard. had been running simple nat setup server 2003: 1 public nic w/static ip connected lan, 1 private nic connected private internal network. internal clients had ips assigned nat dhcp , connecting lan resources internet. worked expected.
public nic (with nat enabled on it)
ip: xxx.xxx.xxx.116
subnet mask: 255.255.255.0
default gateway: xxx.xxx.xxx.1
dns: 4 domain dns servers
private nic:
ip: 10.1.1.1
sm: 255.255.255.0
no default gateway
dns: same 4 domain dns servers
i duplicated configuration upon upgrading server 2008 r2. client ip addresses still being assigned (by dhcp allocator under nat properties). however, external dns servers ignored , internal clients unable internet. can server.
the client machines this:
ip: 10.1.1.xx
sm: 255.255.255.0
gw: 10.1.1.1
dns: 10.1.1.1
if manually enter our standard dns servers on clients, works before. before, server 2003, use dhcp ip dns. i’ve read kb’s find , read through countless forum postings, haven’t found answer yet. i’m missing something. if haven’t given enough information configuration please let me know.
thanks,
fen
if want gateway router able reach public sites in own right, configure isp's dns address or public dns service 4.2.2.2 . if running ad, of private machines should using private dns servers ad works properly. local dns server(s) need contact external dns service resolve public urls ad clients, not router.
set local dns server(s) forward public dns service, such isp's dns server or public service 4.2.2.2 . the client machines should have local dns server(s). eg
internet
|
public ip
xxx.xxx.xxx.116 dg xxx.xxx.xxx.1 dns xxx.xxx.xxx.yyy
nat
10.1.1.1 dg blank dns blank
|
lan machines
10.1.1.1 dg 10.1.1.1 dns local ad servers set forward public dns
bill
Windows Server > Network Infrastructure Servers
Comments
Post a Comment