Bruce Campbell writes: > Nameserver IPs collected at time of request, onus on > client/requestor to ensure that they are kept up to date. Yes, that's how delegations work. RFC 1034: ``The administrators of both zones should insure [sic] that the NS and glue RRs which mark both sides of the cut are consistent _and remain so_.'' (Emphasis added.) As for the frequency of changes: Yes, you have to be notified whenever the server's IP address changes. On the other hand, you're already dealing with changes in the NS names. Sensibly chosen in-zone NS names (a.ns, b.ns) have the advantage of lasting forever. The overall effect on the frequency of changes could be positive or negative. ---Dan
- Re: Should a nameserver know about itself? Cathy Murphy
- Re: Should a nameserver know about itself? Robert Elz
- Re: Should a nameserver know about itself? Bill Manning
- Re: Should a nameserver know about itself? Robert Elz
- Re: Should a nameserver know about itse... D. J. Bernstein
- Re: Should a nameserver know about itse... Shane Kerr
- Re: Should a nameserver know about itse... bert hubert
- Re: Should a nameserver know about itse... Robert Elz
- Re: Should a nameserver know about itse... Bruce Campbell
- Re: Should a nameserver know about itse... Bill Manning
- Re: Should a nameserver know about itse... D. J. Bernstein
- Re: Should a nameserver know about itse... Robert Elz
- Re: Should a nameserver know about itse... Shane Kerr
- Re: Should a nameserver know about itse... Robert Elz
- Re: Should a nameserver know about itse... George Michaelson
- Re: Should a nameserver know about itse... Bruce Campbell
- Re: Should a nameserver know about itse... Mark . Andrews
- Re: Should a nameserver know about itse... James Raftery
- Re: Should a nameserver know about itse... D. J. Bernstein
- Re: Should a nameserver know about itself? Cricket Liu
- Re: Should a nameserver know about itself? Robert Elz
