8.2.3-REL and Slave Zone Problem
Jim Reid
jim at rfc1035.com
Tue Aug 28 10:33:48 UTC 2001
>>>>> "Markus" == Markus Becker <mbecker2 at hrzpub.tu-darmstadt.de> writes:
Markus> Hi, maybe this is an FAQ, but I'm experiencing the
Markus> following Problem w/ BIND 8.2.3-REL: The Server in
Markus> question -let's name him dns_a- shall be slave for
Markus> sub-zone local.mydomain.com. All other requests are
Markus> forwarded (via the forward-statement) to a server dns_b,
Markus> which itself is only a forwarder. A third host, dns_c, is
Markus> master for local.mydomain.com as well as mydomain.com.
Markus> What happens is this: Requests for local.mydomain.com are
Markus> handled locally, but dns_a does not update himself for his
Markus> slave-domain, because dns_b (which is not within my reach)
Markus> returns a "non authoritative for zone
Markus> local.mydomain.com". The same configuration however DID
Markus> work on another machine which used to be dns_a and had a
Markus> BIND 8.2.2 installed. Could this be a bug or is it just a
Markus> mistake by myself ? What would you suggest to solve this
Markus> problem ?? Thanks in advance
You would get along a lot better if you gave the actual names and
addresses instead of this mydomain.com and dns_[abc] nonsense. Why
hide revelant information? What's the big secret? FYI mydomain.com is
a real domain name and it works just fine. However it doesn't have a
subzone called local.mydomain.com.
If the master server for some zone is not authoritative, there is a
local configuration error: for example syntax errors in the zone file.
These errors will be reported in the master server's logs. Get the
administrator of that server to read them and fix the errors. When a
server is not authoritative for a zone, it is not possible to make
zone transfers of the zone.
More information about the bind-users
mailing list