Win2k Domain and domain names on cable setup problems...please help ...

Hello all,

First of all, thanks for taking the time to read such a long post...but I am trying to explain it the best way possible so less typing everyone has to do.

HARDWARE SETUP :

ISP (Static IP) ->  Netgear Router RT314 ( DHCP Server) -> Netgear Switch -> - Win2k Server (Domain Controller - server1)
                                                                                                                  - Win2k Server ( www - ftp - server2)
                                                                                                                  - WinXP Pro (PC - client1)
                                                                                                                  - WinXP Pro (Laptop - client2)

I have a cable connection coming from my ISP with a pretty much dedicated IP (same for the passed 3 years) that is connected to a netgear router which is my DHCP server at the moment with ip (192.168.0.1).  From there, it goes to a netgear switch where it gets connected to my whole home network which includes 2 other win2k servers and 2 winxp clients.

PROBLEM :

Had my home network for all these years under a regular WORKGROUP and 2 days ago decided to play around with domains and the such.  Bought a book on win2k server (sybex-mastering win2k server second edition) and registered a domain name (mydomain.com).  I installed win2k server with service pack 4 and all necessary updates on my main server which i made my domain controller.  Created Active Directory, set it up following the books directions and everything seems to be running great in terms of having the clients joining the domain and users rights etc etc.  when I ping all the computers internally (ftp.mydomain.com or client1.mydomain.com), they all resolve to their respective IP addresses, which tells me that my DNS setup (forward and reverse lookup zones) are working good.

Now, the problem arises when I changed the NameServers on the hosting company(directnic).  I registered 2 new nameservers pointing to the IP that my ISP has been giving me for the passed 3 years and when I try to ping my domain from another computer outside my network ( different ISP), it starts resolving to my internal network IPs, like this :

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\NONNOS>ping www.mydomain.com

Pinging www.mydomain.com [192.168.0.2] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\DOCUME~1\NONNOS>ping controller.mydomain.com

Pinging controller.mydomain.com [192.168.0.8] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.8:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\DOCUME~1\NONNOS>      

(this is all done from a computer outside my network.  Its actually my inlaws PC that is located across town)

This is where I got stuck, cause I am not sure whats going on and the book doesnt explain such an scenario.  I suspect that has something to do with the DNS setup and the fact that I only have 1 IP accessible from the outside.  My router is receiving the ping requests from outside and sending them to my DNS server (same as my Domain Controller) and resolving them to my internal IPs. Here is how i have them setup (Software wise)

SOFTWARE SETUP :

Router                                          : DHCP Server - IP : 162.198.0.1 - Name (router.mydomain.com)
Domain Controller / DNS Server      : Win2k Server + AD + DNS Service - IP : 192.168.0.8 - Name (controller.mydomain.com)
Client 1 / pc                                  : WinXP Pro - Name (client1.mydomain.com)
Client2 / laptop                             : WinXP Pro - Name (client2.mydomain.com)

NSLOOKUP:

Here is a nslookup from my DomainController / DNS Server :

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-1999.

C:\DOCUME~1\ADMINI~1>nslookup
Default Server:  controller
Address:  192.168.0.8

> ls -d mydomain.com
[controller]
*** Can't list domain mydomain.com: Query refused
> mydomain.com
Server:  controller
Address:  192.168.0.8

Name:    mydomain.com
Address:  192.168.0.8

> set type=any
> mydomain.com
Server:  controller
Address:  192.168.0.8

mydomain.com    internet address = 192.168.0.8
mydomain.com    nameserver = controller.mydomain.com
mydomain.com
        primary name server = controller.mydomain.com
        responsible mail addr = admin
        serial  = 32
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)
controller.mydomain.com internet address = 192.168.0.8
>

All machines and users work fine internally.  All domain names resolve fine with their internal IPs with no problems.

Any advice would be much appreciated.                                

Thanks