This is a discussion on DNS Upstream refresh within the Linux Networking forums, part of the Linux Forums category; After an, otherwise, succesful migration the MX record of the BIND nameserver ended up like this: domain.com. IN MX ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
After an, otherwise, succesful migration the MX record of the BIND
nameserver ended up like this: domain.com. IN MX 10 mail.domain.com instead of: domain.com. IN MX 10 mail.domain.com. (that dot at the end.....sigh) Now I need to refresh the dns information upstream cause some MX servers out there send mail to mail.domain.com.domain.com instead of the correct address. I've corrected the typo, lower the refresh to 5 minutes for the master zone, tunred on notify for the zone. Is there anything else I can do to speed up the update? Specifically is there a way to access an internet dns server and specifically tell it to retrieve the new zone information? thx in advance, bill |
|
|||
|
On Mon, 19 Feb 2007 16:04:06 -0800, billis wrote:
> After an, otherwise, succesful migration the MX record of the BIND > nameserver ended up like this: > > domain.com. IN MX 10 mail.domain.com > > instead of: > > domain.com. IN MX 10 mail.domain.com. (that dot at the > end.....sigh) > > Now I need to refresh the dns information upstream cause some MX servers > out there send mail to > mail.domain.com.domain.com instead of the correct address. > > I've corrected the typo, lower the refresh to 5 minutes for the master > zone, tunred on notify for the zone. Is there anything else I can do to > speed up the update? > Specifically is there a way to access an internet dns server and > specifically tell it to retrieve the new zone information? No, you'd have to get the whole Internet (or at least everyone who sends you mail) to drop their caches. For future reference, drop your TTLs to 5-10 minutes a day or two before making changes like this, to mitigate the effect of errors. Once you are satisfied everything is working, raise them again. You could create an A record mail.domain.com.domain.com with the address of your mail server. As long as your negative caching TTL is sensible (it should be around 10 minutes) this should get your mail flowing again. Regards, Ian |