Dynamic DNS

[Irina Goble]

> 
> > I think update should be done as a single transaction when we have all
> > data (ddns_fwd_name and ddns_rev_name are the base for all updates) and
> > during the transaction it is possible to do all additional RRs for those
> > names (ddns_fwd_name, ddns_rev_name).
> 
> But how to be flexible in dealing with the different needs of different
> people.  Karl's request today being an example.  He wants to be able to
> install differing MX records too.
> 
> This thing could get quite ugly.  I think we need to set up a data
> structure and methodology to remember what has to be "undone" when a lease
> is changed or released, etc.
> 
> b.
> 
	What is the difference between A and PTR RRs?
I still think there should be only two transactions: add and delete.

	ddns_add (lease)
	ddns_delete (lease)
	
on DHCPACK call ddns_add()
on DHCPRELEASE call ddns_delete()
on "ABANDON LEASE" call ddns_delete()
ddns_add can call ddns_delete to remove some leftovers.

	I agreed that there is a need for additional RRs (MX, TXT, KEY, etc),
that is what I meant by "additional RRs". All these "additional RRs" are
related to ddns_fwd_name or ddns_rev_name, right? So it is not only a trigger
it is a base domain name for update requests. It could be easy to 
connect add. RRs to PTR by having some parameters/declarations in 
global/subnet/host declarations? But e.g. for MX RRs it is logical to 
connect add. RRs to DNS domains and it could be some additional syntax
in dhcpd.conf. Then _somehow_ we can have all this ns_updrec connected to
a lease structure. 
	struct lease {
	...
	char *ddns_fwd_name;
	char *ddns_rev_name;
	struct ns_updrec *ddns_fwd_upd;	/* additional RRs for a ddns_fwd_name */
	struct ns_updrec *ddns_rev_upd;	/* additional RRs for a ddns_rev_name */
	...
	int flags;
#	define SOME_GOOD_NAME /* for a flag saying who is responsible for
dyn. updates for a forward name, client or server */
	
> --
> Brian J. Murrell                                        
Brian_Murrell at bctel.net
> BCTel Advanced Communications                                      604 454 
5279
> Vancouver, B.C.
>