On Fri, Mar 25, 2005 at 11:31:31AM -0800, Robert L Mathews wrote: > > What you're sort of saying is "I know that in the general case, > nameserver hosts need to be updated at the respective registry when > their IP address changes, but I happen to know that there is something > about these three nameserver hosts which should cause the registry to > never announce glue records, and I therefore don't want to bother > updating them at the registry when they change".
Yes indeed! Except that it's not only that I happen to know it, I tried hard to arrange it that way. > That's dangerous, > really: even if the registry didn't hand out undesirable glue records in > the case of geezer.org, you'd be in trouble if you ever changed ispc.org > to use a ns[0-9].ispc.org nameserver. The registry *would* then have to > hand out glue records, and they would be wrong unless you had remembered > to fix them. OK, I see that. And with a little thought, I can understand that it's hard for the registry to be able to figure out whether there's any self-dependency or loops, and so, as you say: > So even if you don't expect the .org registry to hand out glue records > for your nameserver hosts, I think you should still make sure that the > IP address on file for that host at the registry is correct. That way > everything always works. that makes a lot of sense. Thanks Robert and Dave for the excellent help and education. -mm-
