Local Primary & Secondary DNS Settings

I am currently running a Windows 2003 server and have the DHCP server send out the Windows server as the primary DNS.  But, with this setup the internet goes down everytime I reboot the machine or if it goes down even though the secondary DNS is the primary WAN DNS.  Would it be better to setup the Primary WAN DNS as the Primary LAN DNS and the Secondary DNS as the Windows 2003 DNS?  If that makes sense.

Thank You,
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

If you are often rebooting the current primary DNS server then yes I would set the WAN DNS as the primary (presuming this has more uptime) but ONLY as long as it holds a replica of the DNS Zone(s) you are using. Active Directory relies very heavily on DNS, and things will start to break almost immediately if the secondary DNS server does not have an up-to-date copy of the Zone.
However, you could check your DHCP Scope options to ensure the secondary DNS servers IP is being pushed out correctly as the clients *should* fall back to the secondary DNS server if they fail to get a response form the primary one.
Is the secondary DNS server running OK and responding to lookups?
SNUEngineerAuthor Commented:
Yes the secondary DNS server is running correctly.  It is the one I am getting from the ISP.  The network always seems more stable when the primary DNS is the A/D server.  So if I put the A/D as the secondary you think it would could cause intermittent connections?
SNUEngineerAuthor Commented:
here is my example:

DNS1: (A/D)
You won't be able to do that on a domain, or at least it is not advisable- you need the Active Directory DNS server to be the first point of call to ensure speedy domain related functionality (on a domain controller ideally). Your ISP's DNS server will not have any AD related records on it (SRV records etc) so your domain will very likely start to fall apart.
Do you have a second server you can install a DNS server on (preferably a domain controller) and use this as the primary one?
Unfortunately DNS in the most integral part of Active Directory so what you are trying to do would probably lead to a massive headache for yourself.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
You may be better off addressing the issue(s) that results in frequent reboots of your AD DNS server, instead of trying to change DNS servers.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.