Re: [dhcwg] DDNS-DHCP [6]: Relationship between DNS TTL and DHCP lease length

-----BEGIN PGP SIGNED MESSAGE-----

I came to this thread late.

I can understand why this topic came up in the context of DHCP, but it is
really a dynamic update issue. I use nsupdate to update the location
of my laptop. I do this from my dhcp-client, my ppp "ip-up", and from
some manual scripts that I use when all of the above is not useful.
(which is less often, fortunately)

The reason that I say that dhcp is not involved is because it is my
laptop (not the dhcp server) that has the relationship with my forward
domain server.

As such, what I really want is a dynamic update operation which actually
says "install this record with TTL=XXX, deleting the record after YYY"
(Clearly, XXX < YYY, and some may argue YYY:=XXX. I'm undecided)

I have really no problem sending a new update every couple of minutes.
In fact, I'd prefer to do this.

That way, the record goes away sometime after I go away or I loose
connectivity, which is a lot better than the next time I get online!
(And there are lots of places where DNS is forced-proxy, and dyn-update
does not work. I started a list earlier this month, even:
     http://www.sandelman.ca/mcr/hotels/ actually)

In the reverse map space, and in the places where the dhcpd server does
control the forward map, sure - TTL should be less than lease time, and the
dhcpd server SHOULD remove the record when the lease is returned to the pool.
A timed-dynamic update would be easier for that situation too, I think.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBPvJddoqHRg3pndX9AQG6CAP+Pz9gE5VzA5zmVyRrp7Lam7nMb/9USI5L
nkQUQe7vqrVbwk6Ss8AMFM5+ZLRTCZEJ/3KfBMZqcrhMdaTDhIaOM3LnsPXYhn7p
15QkliFrn5DMd4AZKfgOLxgUN+EKEq/PY3E8bR0a2eWyrJct5nuQbRyeu/9Of2DQ
7/Jeme7A2Cw=
=5++K
-----END PGP SIGNATURE-----

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg