How to setup DNS

  • Thread starter Thread starter Ram
  • Start date Start date
R

Ram

In our company, we have a ADSL offers us some public
IP's. Need help for these scenarios

1) Wind 2k Server with IIS Web server running, it does
not have a name registered with Internic. The persons
connecting the web site directly contact the IP address
(Only very few so its ok). My clients inside the DOMAIn
are directly accessing my ISP's DNS servers address (for
resolution of the outside www pages). How to setup the
DNS server in my machine as a forwader or cache only?

I want all my clients for outside request to contact my
local server first (as it will act as forwarder/cache
server). If its not in its cache then it should forward
the request to my ISP's DNS server & store it in cache.
So less DNS queries goes out.

How to setup those servers in the AD? Any links

2) If I have a registered name with my PUBLIC IP, then
how to setup my DNS server to resolve my IIS server to
the outside world & my local machines queying other local
machines? or I can outsource DNS resolution alone
outside? If so who are you recomending in Australia?

We are planning to run a web server
 
In
Ram said:
In our company, we have a ADSL offers us some public
IP's. Need help for these scenarios

1) Wind 2k Server with IIS Web server running, it does
not have a name registered with Internic. The persons
connecting the web site directly contact the IP address
(Only very few so its ok). My clients inside the DOMAIn
are directly accessing my ISP's DNS servers address (for
resolution of the outside www pages). How to setup the
DNS server in my machine as a forwader or cache only?

I want all my clients for outside request to contact my
local server first (as it will act as forwarder/cache
server). If its not in its cache then it should forward
the request to my ISP's DNS server & store it in cache.
So less DNS queries goes out.
Click to expand...

In an AD environment all clients and servers including and especially the
DCs must point to the internal DNS server ONLY. Using your ISP's DNS in any
NIC will cause many problems, errors and slow logons. Your ISP's DNS should
only be used as a forwarder in your internal DNS server on the Forwarders
tab. If the forwarders tab is grayed out, you need to delete the "." Forward
Lookup Zone. This will enable Root Hints and allow you to use a forwarder.
Read 300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1
How to setup those servers in the AD? Any links

2) If I have a registered name with my PUBLIC IP, then
how to setup my DNS server to resolve my IIS server to
the outside world & my local machines queying other local
machines? or I can outsource DNS resolution alone
outside? If so who are you recomending in Australia?
Click to expand...

One DNS server cannot do both internal DNS and Public DNS for the same
domain name if you are behind a router or other NAT device. I recommend you
outsource the public DNS. Your internal DNS will need a forward lookup zone
for the same name but the records in your internal DNS will give your
internal users private IPs to access your internal sites and servers.
Domain Name System (DNS) Center
http://www.microsoft.com/Windows2000/technologies/communications/dns/default.asp
 
Back
Top