Bernd Wurst <[EMAIL PROTECTED]> writes: > Hi. > > Am Mittwoch, 15. März 2006 18:07 schrieb Lloyd Zusman: >> Gordon Messmer <[EMAIL PROTECTED]> writes: >> > Lloyd Zusman wrote: >> >> I handle this user's email with my Courier server, and I'm >> >> wondering if I need to do a "courier restart" every time his DNS >> >> changes. >> > I can't think of any reason why you would. Is there something >> > specific that you expect to break? >> No. I just want to make sure that nothing _does_ break. > > Do you have the possibility to set the DNS-time-to-live for your > record(s)? > > Without knowing the code of courier, I would bet that courier fits to > the dns specs, so if you set the dns TTL of your record to something > low, possibly 0 or 1, courier should not attept to cache your records > longer than that time. > > cu, Bernd
I'll investigate this. I'm using tinydns, and I seem to recall that TTL isn't overly configurable. But even if it's not, will that matter? When would Courier need to know the resolution of the "A" record for the domain part of an email address that it's serving? And recall that the "MX" record for this user remains constant (it points to this same Courier server). Also ... if it turns out that I would have to restart Courier in this case, is "courier restart" sufficient, or would I have to restart all of the Courier-related daemons? Thanks. -- Lloyd Zusman [EMAIL PROTECTED] God bless you. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
