No subject


Tue Apr 2 00:56:56 UTC 2013


this domain if (a) its configuration file says that it is (i.e., either
a master or a slave - which makes no difference in this case), and (b)
it has the zone information (from a zone file or from another server),
and (c) it does not detect any errors in the zone information.

Errors in the zone information mean that a server may have the
information, but doesn't consider itself authoritative for it.  An
error in the configuration file or a lack of zone information may make
a server that YOU (the human) think is authoritative, not
authoritative.

NOTE THAT THESE TWO MEANINGS HAVE (unfortunately) NOTHING TO DO WITH
EACH OTHER.  Unless they coincide by the co-operation of the people who
are configuring the various servers.

A server may believe itself to be authoritative for a domain.  And for
those who think to query it, it is.  But if there is no parent server
out there delegating authority for that domain, nobody else will ever
know it.  This is GOOD when you are creating separate internal/external
DNS servers.  This is BAD if you desperately want the Internet to know
you are there, but nobody is delegating to you.

A server may be named in an NS record as an authoritative server, but
not believe itself to be authoritative.  This could be because the
server has an error in the zone file, or because it has not been
configured correctly, or because the NS record is wrong, and this
server is not supposed to be a server for this domain.  This situation
is known as a "lame server".  It is BAD.  but only the people
configuring the "lame" server and the server dispensing the "lame" NS
records can fix this.

Hope this helps.

-- 
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.



More information about the bind-users mailing list