I have just installed Windows Server 2003 SP2 on a new server on our new network. We have a registered domain name and have registered the nameserver. When I navigate to the website records on the DNS (from a remote location web browser - not on the network), it takes me to the website. The DNS server also doubles up as a NAT server and internet gateway for the network behind it.
What I am trying to do is add an A record to the DNS server which points to a private (behind the NAT, 192.168.x.x) address. Although, let's say I made the A record test.domain.com. It also points to 192.168.1.11, for example. From within the network, the record allows me to get to that webserver. When I try to access the same record from a remote location, it does not connect and gives me an error 400.
Can anyone please help me to learn how to set up a DNS server correctly in this situation? Remember, though, the DNS is also the gateway/NAT server.
What I am trying to do is add an A record to the DNS server which points to a private (behind the NAT, 192.168.x.x) address. Although, let's say I made the A record test.domain.com. It also points to 192.168.1.11, for example. From within the network, the record allows me to get to that webserver. When I try to access the same record from a remote location, it does not connect and gives me an error 400.
Can anyone please help me to learn how to set up a DNS server correctly in this situation? Remember, though, the DNS is also the gateway/NAT server.