Y
Yui
Hi Herb,
Thank you for your reply. Please see my comments inline below:
The DNS with the 10.x.x.x is in DMZ. The unit is not equiped with two
NICs, but one. I read on some article that Windows2000 DNS can
possibly handle this configuration, DNS with NAT, although BIND can
deal with this without question.
The DNS server with the 10.x.x.x above.
I can neither do nslookup the DNS server from the internet, nor do
nslookup itself with DNS querries' timeout...
Thanks, I checked the above points, but nothing has been resolved...
Let me summarize how I want to setup the systems as below:
External(Outside): Firewall
[External<->DMZ - NAT (60.x.x.x <-> 10.x.x.x)
DMZ: DNS with private IP (10.x.x.x)
- Service - Only DNS
- NIC x 1
- DNS Zone File, etc., -> Global IPs
[External<->Trusted - NAT (60.x.x.x <-> 192.x.x.x]
Trusted(LAN):
- DC Server with Private IP (192.x.x.x) and dynamic for the zone
- Client Pool
-- Primary DNS -> DC Server (Private IP)
-- Secondary DNS -> DNS Server (Private IP)
I can reach the internet from any of client PCs with the setting
above.
Do I need configure any additional parameters on the DNS server?
Please advise,
Thank you for your reply. Please see my comments inline below:
Where is the 10.x.x.x machine? Or are those two NICs on
one machine?
The DNS with the 10.x.x.x is in DMZ. The unit is not equiped with two
NICs, but one. I read on some article that Windows2000 DNS can
possibly handle this configuration, DNS with NAT, although BIND can
deal with this without question.
Which server?
The DNS server with the 10.x.x.x above.
I can neither do nslookup the DNS server from the internet, nor do
nslookup itself with DNS querries' timeout...
Huh?
Any problem (of misconfiguration) can be resolved and
Windows DNS is almost always superior for Windows
domains (over BIND.)
DNS
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) On the internal DNS servers set the ISP DNS server(s) as
the FORWARDER
Restart NetLogon on any DC if you change any of the above that
affects a DC.
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Thanks, I checked the above points, but nothing has been resolved...
Let me summarize how I want to setup the systems as below:
External(Outside): Firewall
[External<->DMZ - NAT (60.x.x.x <-> 10.x.x.x)
DMZ: DNS with private IP (10.x.x.x)
- Service - Only DNS
- NIC x 1
- DNS Zone File, etc., -> Global IPs
[External<->Trusted - NAT (60.x.x.x <-> 192.x.x.x]
Trusted(LAN):
- DC Server with Private IP (192.x.x.x) and dynamic for the zone
- Client Pool
-- Primary DNS -> DC Server (Private IP)
-- Secondary DNS -> DNS Server (Private IP)
I can reach the internet from any of client PCs with the setting
above.
Do I need configure any additional parameters on the DNS server?
Please advise,