Re: Single Server2003: DNS Settings to Allow Internet When Server Down

Thanks!

"Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message
news:O2mmoAZBHHA.3380@xxxxxxxxxxxxxxxxxxxxxxx
"Karl Burrows" <karlspam@xxxxxxxxxxxxxxxxxxx> wrote in message
news:eFkO9$UBHHA.140@xxxxxxxxxxxxxxxxxxxxxxx
Thanks! Figured this was probably the case. Any good links you can
recommend for setting up 2 DNS servers in 1 domain?

The built in help is more than sufficient. (Doesn't
anyone every read that stuff?)

Key points to keep in mind while reading the Help
or any other source:

Using a Secondary DNS server for the zone versus
using an AD Integrated DNS on multiple DCs is a
key choice.

If you have multiple DCs, then I would strongly urge
you to use AD DNS on the first DC. Ensure replication
and then install the DNS server on the second and
normally the zone will just "show up".


"Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message
news:ua6rWdRBHHA.3836@xxxxxxxxxxxxxxxxxxxxxxx
"Karl Burrows" <karlspam@xxxxxxxxxxxxxxxxxxx> wrote in message
news:OUzqFaIBHHA.4428@xxxxxxxxxxxxxxxxxxxxxxx
Is there a way to setup the DNS so that if the server is down, that
clients
in the domain can still connect to the Internet, email, etc?

Not without another internal DNS server which holds your
zone supporting your AD.

All attempts to list multiple DNS server "sets" on the client
NICs will give unreliable results. Don't do that.

This is one of the reasons you really should have two DCs
although this specific problem is not due to DCs but merely
the DNS.

Running single Server 2003R2 on domain connected to local DSL for
Internet.

If you can afford a relatively obsolete computer to
run as DNS (and maybe DC) then put Windows
Standard Server on it (perhaps the biggest cost so
even Web edition could work if it will not be a DC)
and run DNS.

If you have hardware but cannot afford the license for
the OS then run Linux on it and make the DNS server
there a secondary for you zone.

Barring this, put BIND or another open source/free DNS
server on a workstation and set as a secondary.

You need two internal DNS servers.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]



--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


Thanks!








.

Relevant Pages

  • Re: FQDN cannot be managed because it is not running Windows NT
    ... The DNS server was unable to open zone 18.35.10.in-addr.arpa in the Active ... that the Active Directory is functioning properly and reload the zone. ... event data is the error code. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Local Delivery is not sending to one recipient in Exchange Ser
    ... The DNS server was unable to open zone rickkochoil in the Active Directory ... Errors in File Replication Service: ... Running partition tests on: ForestDnsZones ...
    (microsoft.public.exchange.admin)
  • Re: Error 4515 on reboot of DC/DNS Svr - normal?
    ... switch back to AD with Forest wide, and then put the DNS service ... I do believe you are correct that the "old" zone is still there. ... (replication is for all DNS servers in the forest) ... The key is that your clients have to be able to go to ANY DNS server ...
    (microsoft.public.windows.server.dns)
  • Re: Replication issues
    ... I wanted to say Zone Transfers not Zone Forwarding. ... AD-Integrated DNS does not do zone transfers between the ... your DNS server will bypass ...
    (microsoft.public.windows.server.active_directory)
  • Re: Error 4515 on reboot of DC/DNS Svr - normal?
    ... I did run dcdiag on all DCs, ... I do believe you are correct that the "old" zone is still there. ... (replication is for all DNS servers in the forest) ... The key is that your clients have to be able to go to ANY DNS server ...
    (microsoft.public.windows.server.dns)