(no subject)

Kevin M Shortt shortt at cse.Buffalo.EDU
Tue Mar 6 15:30:59 UTC 2001

I am having some difficulties understanding some of the workings
that are happening with BIND 8. (currently testing with 8.2.2p5)

I exhaustedly searched archives and even read RFC2136.
I am having trouble accepting the following behavior.

Concisively put, I have win2k boxes updating a zone on BIND 8.2.2p5
server. When the win2k box attempts to update an RRSET for itself, the
prerequisite RCODE from BIND 8.2.2p5 is (NXRRSET) gets returned when
the RRset (or A record) was not in the zone already.

NXRRSET as defined in section 2.4.1 (RFC2136) and further explained in
section 3.2.1 (RFC2136) is:
	Some RRset that ought to exist, does not exist.

My Questions:

Why (oh why) must the server error when an attempted update of an RR
doesn't exist. The only known way (to me) to avoid these errors is to
preexist the RR's in my zones. Wouldn't that defeat the purpose of DDNS?

Also when the RCODE NXRRSET rears up, the DDNS seems to work fine, with
exception that the zone file doesn't update until the server process is
stopped or restarted. Why does work and keep in cache, but the zone file
doesn't reflect a serial increment or the changed record?


More information about the bind-users mailing list