Dynamic DNS

Brian J. Murrell brian_murrell at bctel.net
Fri Aug 6 23:11:03 UTC 1999


from the quill of Irina Goble <irinag at ims.com> on scroll
<199908062240.PAA26774 at speed.ims.com>
>  
> > 1	prereq: {yxdomain} h.example.com. IN A 
> > 2	update: {delete} h.example.com IN A
> > 3	update: {add} h.example.com. 600 IN A 192.168.1.1
> > 4	prereq: {yxdomain} 1.1.168.192.in-addr.arpa. IN PTR 
> > 5	update: {delete} 1.1.168.192.in-addr.arpa. IN PTR 
> > 6	update: {add} 1.1.168.192.in-addr.arpa. 600 IN PTR h.example.com.

> 	You can try 1,2,3 in one request and 4,5,6 in another, should work,

So your reading of the RFC (or nsupdate code I guess) is that the update
can contain more than one "command"?

> however there is no way to know if an update failed because of the
> prerequsite
> or update section.

Hmmmmm.  Wondering if I care.  I mean it should be reported, that there was
an error, but there is nothing the DHCP server could do about either error.

b.



--
Brian J. Murrell                                        Brian_Murrell at bctel.net
BCTel Advanced Communications                                      604 454 5279
Vancouver, B.C.


More information about the dhcp-hackers mailing list