asked on

DNS Setup, NTS 4.0

Need "quick and dirty" setup for NTS 4.0 DNS, while I
learn how to set up a "real" DNS with all the MX, CNAME,
and whatever records.

For now, I need to use the NT server to "echo" a couple
of existing name servers, which go down a lot. How do I
set up DNS under NTS 4.0 to, for now, CACHE some or all
of the entries from these other two servers, so when,
not if, they go down, our users can point to our new
"reliable" DNS on NT that is cacheing entries (for now).

ASKER CERTIFIED SOLUTION

bgoldstein

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

rjbryla

ASKER

OK, sounds straightforward, but if the primary DNS blows chow,
and someone tries to get a DNS response from the secondary
(the NT server in questions) to a DNS query for a site never
referenced in a lookup, will the secondary still be able to
fulfill the request? Example, if no one has ever gone to the
Microsoft ftp site before (Right!), the primary DNS goes down,
then someone tries to ftp to ftp.microsoft.com, will it work???

bgoldstein

That is exactly right - the secondary server will copy the primary's db files and will basically sit there and wait for the primary to die. He is fully functional at all times - you can even point to him as your primary DNS server. Now, don't confuse primary server and secondary server that the CLIENT points to with primary and secondary as they refer to a DNS server being secondary to to a primary with regards to its db files.

I think what you are referring to is whether the secondary server will develop a cace of addresses, and the answer is no - it will be the same as if you were to cold boot your primary - he starts from scratch. Hope this helps.