How to setup DNS server in this situation?

[Mr.S]

How to setup DNS server in this situation?

I’m using one static IP address with register domain in InterNIC.
Running: Window 2000 SP2, Exchange 2000 on the same machine.
Provider: @HOME
Hardware: Toshiba PCX100 -> UGate 3200 ‘Switch/Router/Firewall’

Right now W2K Server is using one static IP from @HOME (PDC) and all clients are using private IPs (10.0.0.x) from UGate DHCP server. all computers are connected to the switch.

Problem:
When I am adding an additional Server (BDC) to my existing domain for transfer Exchange server with private address, then it look like it works fine. But when I try to use : ‘nslookup.exe domain.com’ from outside of my network, I get an incorrect result: two internal and external IPs. When I try to stop forwarding DNS for internal IP, I get the same incorrect result.

Question:
How to stop forwarding internal IP? (Case when domain (PDC) is using one external IP and an additional domain (BDC) is using internal IP).
Do I have to order second IP for the additional domain? Or may be I can do a tricky setup?

I will be grateful if you can advise me on this matter.

Thanks.

[MosDef112]

Since @Home only assigns you a single static IP, and chances are this IP is bound to it's own name servers from @Home, you would need an additional IP from @Home if you wish for this second PC to be publicly pingable, and for it to handle a second publicly available domain. You could, however, bind multiple domains to your single public IP from @Home, but they would point to the same services you setup since there is no way of telling your server how to handle requests for different domain name queries. You could setup your own DNS server so that hosts within your private LAN get a response while pinging a host within your own domain, like testpc1.testdomain.com. Another way of taking a crack at it is by making your registrar forward requests made to a domain, to a different domain. For example, you can have InterNIC forward all DNS lookups and mail exchange for domain testdomain.com to testdomain2.com. This gets intricate because you must also setup your main Exchange server to forward all mail coming in for domain testdomain.com to testdomain2.com, and have your secondary Exchange server accept mail inbound for that domain. So to finally answer your question: No, you don't need a second IP to handle a second domain name, but you do need to setup your main Exchange server to listen in for both domains, and have that Exchange server forward all mail intended for the second domain, to your second Exchange server. It's easier to get a second IP, but you could also save money by doing my suggested setup.