How to Change/Move Domain smoothly
cbuxton at menandmice.com
Wed Jun 4 16:44:59 UTC 2008
Most likely, the SOA record values will have no effect at all on your
changeover. Lowering the refresh time just causes the slave servers to
check in more often for zone updates. With a modern version of BIND
and correctly set up NS records, the master will notify the slaves
whenever the zone is updated, making the refresh interval a fallback
mechanism that's rarely needed.
It would be better to focus your efforts on the TTL's of the MX
records in question. Ignore the SOA record.
To check your changes with dig, just ask the server in question about
the record in question. For example:
dig example.com soa @ns1.example.com +norec
dig example.com mx @ns2.example.com +norec
The "+norec" causes dig to send iterative queries instead of recursive
queries. This is good for debugging and testing.
Men & Mice
On Jun 4, 2008, at 2:01 AM, ml at bortal.de wrote:
> Hello List,
> i would like to change the MX record of a few domains.
> Whats the best way to do this?
> Right now i have set it to:
> 15m ;refresh
> 1h ;retry
> 7d ;expire
> Is this okay? Should i lower the retry time, too?
> How can i check my changes with dig?
> Thanks, Mario
More information about the bind-users