View Single Post
  #4 (permalink)  
Old 08-17-2007, 10:51 AM
shaalini shaalini is offline
D-Web Analyst
 
Join Date: Apr 2007
Posts: 342
shaalini is on a distinguished road
Default Re: Windows 2003 server Domain Controler problem

Hi,

This all depends on what you plan to use your DNS server for. If it is going to be used strictly for name resolution for web content, then all you need to do is set the "Pointer" IP Addresses in the configuration on the server. This is where you would input the DNS IP Addresses provided to you by your ISP. Your internal LAN clients would then have the internal IP address of your Windows 2003 box as their DNS Server.

When a client on your local LAN attempts to browse a web page, the request will first be made to the local 2003 box, then the request will be redirected to the "external" DNS IP Addresses of your ISP. Once a name resolution comes back, it will be forwarded to your internal client.

You can also setup zones on an internal basis. For example, if you have nodes on your network with static IP addresses, e.g. printers, servers, access points, that you wish to be able to access via name rather than IP, you could create mappings for these devices.

For example:

printer.yourDomainName 192.168.1.5
server2.yourDomainName 192.168.1.6
accessPoint.yourDomainName 192.168.1.222

And so on....
Reply With Quote