Dynamic DNS

Irina Goble irinag at ims.com
Fri Aug 6 16:24:19 UTC 1999


Hello,

> 
> > I really cannot see adding this ability to the first DDNS method though
> > Ted.  If somebody wants this kind of ability, they will have to use the
> > new DDNS methodology.
> 
> Agreed.
> 
> 			       _MelloN_

	I'm not sure what the first DDNS method means but there is 
definitely a problem with the new DDNS methodology. Please correct me
if I'm wrong. Let's take a look at an example.
An IP address was assigned to a host with vasya.test.com. Now another
computer is getting this address or the old one decided to change a name.
So in DNS we have:
	vasya.test.com. 		IN A 192.168.1.1
	1.1.168.192.in-addr.arpa. 	IN PTR vasys.test.com.
	
	There is no clear "release A,PTR RRs". All removes are done
through a getting a new hostname, right?

	calling updateA(masha.test.com, 192.168.1.1, 600, lease)
	delete succeeded: vasya.test.com 0 IN A 192.168.1.1
at this point we removed lease -> ddns_fwd_name = vasya.test.com	
	add succeeded: masha.test.com 600 IN A 192.168.1.1
at this point we have lease -> ddns_fwd_name = masha.test.com

	calling updatePTR(1.1.168.192.in-addr.arpa, masha.test.com, 600, lease)
at this point: nsupdate(1.1.168.192.in-addr.arpa, masha.test.com, DELETE) but
we have 1.1.168.192.in-addr.arpa. IN PTR vasya.test.com.

	Brian, I don't see how it can work, Please explain this.
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).

Irina



More information about the dhcp-hackers mailing list