DNS, PDC, and and Internet Server

Hi, i'm new to this board, I'll go straight to the problem

I work in a company, and we have
* 40 computers (192.168.0.x) running Microsoft Windows XP Professional

* 1 Primary domain controller (192.168.0.1) to control user names/policies..etc running MS Windows 2000 Server, and

* another computer (192.168.0.10) running Windows 2000 Server (that i wish to use as an Internet Server).

* a Linkstar earth station (Internet-via-Satellite system) [IP=10.86.0.49] No public IP just private IP range of (10.86.0.50-10.86.0.62)

The computer that i wish to use as an Internet Server (192.168.0.10) has 2 network cards, as follows:

---public interface (Connected to the earth station)
IP=10.86.0.50,
Gateway=10.86.0.49 (the earth station)
DNS1= 213.140.2.12 (supplied by my ISP)
DNS2= 213.209.161.87 (supplied by my ISP)

---Local Interface (Connected to the company hub)
IP=192.168.0.10
Gateway= none
DNS=none

The problem:
Clients can use the active directory resources, log in and use network resources only when their Primary DNS = 192.168.0.1 (the PDC IP)

Clients can use the internet pretty well, when their Primary DNS = 192.168.0.10 (the Internet Server, Internet server's Firewall application uses its own DNS server to forward packets to public DNS Servers)

But Clients can't use both the Active Directory and browse the Internet at the same time. (this is the problem)

Note: Microsoft DNS Server on the PDC can't use forwarding nor root servers. (Disabled, cause it's a root server).

I tried to configure another machine (193.168.0.3) as a DNS Server to Forward DNS queries to the 192.168.0.1 (PDC) and 213.140.2.12 (Public Network), and here's what happened (I used CommView to watch packets):

192.168.0.3 receives queries -regarding local domain or public network- at port 53
but it always forwards them to 192.168.0.1 (the first in the Forwarding list) at port 137 not 53.

when i use only public DNS servers in the Forwarding list (213.140.2.12 and 213.209.161.87) the DNS Forwarder does its job pretty well. (i.e. checks 213.140.2.12 first, and moves to 213.209.161.87 if it couldn't get an answer from the first).

I hope if there's another way other than updating the HOSTS or LMHOSTS files on all client workstations.

I think i need some help regarding how to set up a the DNS Server that comes with Windows 2000 Server as a Forwarder to 2 DNS servers (Local=192.168.0.1 and Public=any Public DNS) with as much detail as possible.

Thank you...
Anmar

I'm not much of a Windows DNS user, but I hope this doc will help:
http://www.microsoft.com/servicepro...s/split_dns.asp

If only people would use BIND dns server then I can make it do jumping jacks to fit any scenario. Unfortunately you're using Microsoft DNS Server and I'm not so familiar with that server. But I will tell you the theory behind how I would do it on BIND, and maybe you can find a related feature on Microsoft DNS Server.

You probably have private domains on your network for network resources. This private domain might be something like "network.local" or something with each computer having a name like "jack.network.local" etc. If you had BIND installed on the internet server, then I would configure all machines on the network to use the internet server for domain resolution. Then I would setup the "network.local" on the BIND server as a forward zone (or shoot, you could even forward all *.local requests). All requests for "*.network.local" would be forwarded to the PDC. All other requests would be forwarded to the ISP dns servers.

So look for something like that in Microsoft DNS Server. The page that scorpion gave you is useful for a different situation entirely where you have a private space and a public space for the same domain.

I don't want to interrupt here, because I can't really help... but isn't that just a completely pointless post?

Pretty much, but I wasn't going to raise a fuss over it. I mean, what am I going to say? "thank you" and encourage him? Or am I going to say politely "please don't make posts that aren't helpful"? Then he'll feel like the compliment wasn't appreciated and may be bitter over a really nothing thing. Not to mention talking about it brings the entire topic off subject. So ignoring such comments is the best way to go.

Well, thank you all, i think i'll configure a DNS Forwarder, or try BIND