DNS setup

  • Thread starter Thread starter wilbur
  • Start date Start date
W

wilbur

Hi,
I have a small win2K domain, 2 DCs, about 35 machines.
Both DCs are running DNS AD integrated, 192.168.0.250 and
251. I have a PIX firewall running DHCP. Should I use the
DNS IPs of the DCs in the DHCP assignments, or the public
IPs from our ISP?
Thanks - Wilbur
 
Definitely use your internal dns for your clients and not the ISP.
You can set up a Forwarder in dns on each machine if desired to do the ISP,
but all internal servers/clients should Only point to your internal win2k
dns server/s. The forwarder will then handle any request for something it
doesn't know, and "forward" to the isp and return reply.

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
 
Thanks - So I set the DNS entrys to point to the DCs in
DHCP. Do I point the DCs to themselves for DNS? Where to
I set up a forwarder?.
- Wayne
 
With two dc's there are a couple of ways to do it and both seem to work ok.
You can either point each dc to iteslf as primary and then the other dc as
alternate, or point both dc's to one for primary and then both to the other
as alternate.
If you do properties on the "server name icon" under dns you should see a
Forwarders tab where you can set them there. Any request that the dc then
gets that it can not resolve it will forward out to whatever address/es are
in there. Forwarders info is not replicated, so if you wanted it on both
dns boxes you'll need to add it to both.
If it is grayed out, you still have a "." forward lookup zone (which means
the box thinks it is a "root" dns server like com, net, org, etc and will
need to be deleted before forwarders can be set). No need to forward if I
am the root <g>
That zone can be recreated again later if for some reason you wanted it
back.
After it is deleted, it takes a bit for the Forwarders tab to become active,
but you can speed that up by stopping/re-starting dns service.

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
 
Thanks - got everything up working fine...
-----Original Message-----
With two dc's there are a couple of ways to do it and both seem to work ok.
You can either point each dc to iteslf as primary and then the other dc as
alternate, or point both dc's to one for primary and then both to the other
as alternate.
If you do properties on the "server name icon" under dns you should see a
Forwarders tab where you can set them there. Any request that the dc then
gets that it can not resolve it will forward out to whatever address/es are
in there. Forwarders info is not replicated, so if you wanted it on both
dns boxes you'll need to add it to both.
If it is grayed out, you still have a "." forward lookup zone (which means
the box thinks it is a "root" dns server like com, net, org, etc and will
need to be deleted before forwarders can be set). No need to forward if I
am the root <g>
That zone can be recreated again later if for some reason you wanted it
back.
After it is deleted, it takes a bit for the Forwarders tab to become active,
but you can speed that up by stopping/re-starting dns service.

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.



.
Click to expand...
 
I have a related question:

We have W2K DNS setup with forwarders. We also have host
records for internal websites so DNS resolves them
instead of going to the DNS of the ISP.

How do I have a www record of a internal website redirect
to a specific page on another website?

Thanks!

Rajeev Sajja
(e-mail address removed)
 
In Rajeev Sajja <[email protected]> posted a question
Then Kevin replied below:
: I have a related question:
:
: We have W2K DNS setup with forwarders. We also have host
: records for internal websites so DNS resolves them
: instead of going to the DNS of the ISP.
:
: How do I have a www record of a internal website redirect
: to a specific page on another website?
:
: Thanks!
:
: Rajeev Sajja
: (e-mail address removed)
:
:: -----Original Message-----
:: Definitely use your internal dns for your clients and not the ISP.
:: You can set up a Forwarder in dns on each machine if desired to do
:: the ISP, but all internal servers/clients should Only point to your
:: internal win2k dns server/s. The forwarder will then handle any
:: request for something it doesn't know, and "forward" to the isp and
:: return reply.
::
:: --
:: David Brandt
:: Microsoft Corporation
::
:: This posting is provided "AS IS" with no warranties, and confers no
:: rights. Please do not send e-mail directly to this alias. This alias
:: is for newsgroup purposes only.
:: ::: Hi,
::: I have a small win2K domain, 2 DCs, about 35 machines.
::: Both DCs are running DNS AD integrated, 192.168.0.250 and
::: 251. I have a PIX firewall running DHCP. Should I use the
::: DNS IPs of the DCs in the DHCP assignments, or the public
::: IPs from our ISP?
::: Thanks - Wilbur
::
::
:: .

Create a website that the www record would resolve to, then on the Home
Directory Tab in IIS redirect to a URL, then put in the URL in another
domain of the page you want it to go to.
 
Back
Top