DNS server not refreshing

[Kevin Darcy]

Kevin Darcy wrote:

> The persistence of DNS information is controlled by the domain master for both
> caching (via TTL settings on the records) and authoritative servers (via the
> "refresh" parameter in the SOA). If you have a problem with changes not
> propagating in a timely fashion, then it's likely to be one or both of those
> things.
>
> Another complication, however, is "glue records". These are records held in the
> parent domain whenever a nameserver for the child domain is actually in the
> domain itself, e.g. if ns.foo.com is a nameserver for foo.com. If you use
> ns.foo.com for mail as well as DNS, and change its IP address, then it has to
> be changed in *two* places: in the zone itself, and in the glue records.
> Failure to change the glue records will cause the old address to be cached
> *some* of the time, which can result in intermittent failures.

Actually, what I should have said is that it should be changed in both places,
regardless of what the box is used for. But if you fail to change the glue
records, the impact is likely to be greater if it's used for other things besides
DNS...


- Kevin