Archived from groups: microsoft.public.win2000.dns (
More info?)
"Dave" <Dave@discussions.microsoft.com> wrote in message
news:0E36CBE5-ABE7-47A5-A132-17C353AE5FB5@microsoft.com...
> Thank you, Herb.
>
> To clarify, these are not AD-integrated zones (or, at least, have nothing
to
> do with our AD network). In fact, these are our public-facing DNS servers
in
> a split-brain configuration. Our other, internal DNS servers are indeed
> AD-integrated.
The confusion was due to your writing 'file *instead of AD'
(implying you had store it in AD):
Since it is a secondary then it is very likely that your zone
EXPIRED (too long without transferring from master, e.g.,
the primary.)
> > > was not storing local copies of the DNS records? Does this mean I
should
> > > select "File" storage instead of "Active Directory and Registry?"
If you are at a secondary you should be able to force a transfer
from master (before you lost your primary) and see any changes
update.
> Does this mean that I should set "Load zone data on startup" to "Registry"
> or "File?"
Registry or file matters very little.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
>
> Dave
>
> "Herb Martin" wrote:
>
> > > My primary DNS server failed the other day and, to my surprise, our
> > > secondary DNS server stopped serving DNS queries soon after.
Apparently,
> > it
> > > was not storing local copies of the DNS records? Does this mean I
should
> > > select "File" storage instead of "Active Directory and Registry?"
> >
> > The above offers inconsistent descriptions.
> >
> > AD Integrated DNS servers are NOT "secondaries" but a special
> > form of a multi-Mastered Primary -- most of us don't use the word
> > primary for them although the newer document for Win2003 does
> > call them a Primary that stores records in AD.
> >
> > In any case if you have two AD Integrated DNS servers for a zone,
> > neither is a secondary (for that zone.)
> >
> > However, since AD is dependent on DNS for replication, if you
> > had failed to setup DNS correct first (before moving the zone into
> > AD on the second server) then the failure to replicate AD would
> > of course fail also to replicate DNS.
> >
> > > Any other
> > > recommendations for secondaries I should know about before our primary
> > fails
> > > again?
> >
> > Make sure that all AD Integrated DNS servers are fully replicate
> > both before you change additional ones to AD integrated and thereafter.
> >
> > DNS must work for AD before it will work for AD Integrated DNS...
> >
> > 1) Dynamic for the zone supporting AD
> > 2) All internal DNS clients NIC\IP properties must specify SOLELY
> > that internal, dynamic DNS server (set.)
> > 3) DCs and even DNS servers are DNS clients too -- see #2
> > 4) If you have more than one Domain, every DNS server must
> > be able to resolve ALL domains (either directly or
indirectly)
> >
> > netdiag /fix
> >
> > ....or maybe:
> >
> > dcdiag /fix
> >
> > (Win2003 can do this from Support tools):
> > nltest /dsregdns /server
C-ServerNameGoesHere
> > http://support.microsoft.com/kb/q260371/
> >
> > Ensure that DNS zones/domains are fully replicated to all DNS
> > servers for that (internal) zone/domain.
> >
> > Also useful may be running DCDiag on each DC, sending the
> > output to a text file, and searching for FAIL, ERROR, WARN.
> >
> > Single Label domain zone names are a problem Google:
> > [ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
> >
> >
> >
> > --
> > Herb Martin, MCSE, MVP
> > Accelerated MCSE
> >
http://www.LearnQuick.Com
> > [phone number on web site]
> >
> > "Dave" <Dave@discussions.microsoft.com> wrote in message
> > news:10869559-9432-4184-8C2D-2AF5C0F64133@microsoft.com...
> > > Hi all,
> > >
> > >
> > > Thank you!!!
> > >
> > > Dave
> >
> >
> >
Facebook
Twitter
Instagram