Date: Sat, 26 Nov 2005 19:31:35 -0800 From: Greg Maruszeczka <greg@grokking.org> To: freebsd-questions@freebsd.org Subject: Re: MX freebsd Message-ID: <43892897.7010507@grokking.org> In-Reply-To: <6.2.3.4.2.20051126152021.07ae8140@cobalt.antimatter.net> References: <20051120105719.19460df6.dick@nagual.st> <cone.1132965821.647439.5396.5001@35st-server.simplicato.com> <200511251553.17891.akbeech@gmail.com> <6.2.3.4.2.20051125171610.02addb80@cobalt.antimatter.net> <4388A23E.8080208@grokking.org> <6.2.3.4.2.20051126152021.07ae8140@cobalt.antimatter.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Glenn Dawson wrote: > At 09:58 AM 11/26/2005, Greg Maruszeczka wrote: > >> Glenn Dawson wrote: >> > At 04:53 PM 11/25/2005, Beecher Rintoul wrote: >> > >> >> On Friday 25 November 2005 03:43 pm, Francisco Reyes wrote: >> >> > dick hoogendijk writes: >> >> > > Any idea how long it takes until the MX freebsd mailservers >> know that >> >> > > my mail relay has changed? It's three days ago now that I changed >> >> my MX >> >> > > records and still mail for nagual.st is routed to my old mx >> >> > > mailservers. >> >> > > >> >> > >dig nagual.st mx >> >> > >> >> > ;;; QUESTION SECTION: >> >> > ;nagual.st. IN MX >> >> > >> >> > ;; ANSWER SECTION: >> >> > nagual.st. 86400 IN MX 10 mx1.mailhop.org. >> >> > nagual.st. 86400 IN MX 20 mx2.mailhop.org. >> >> > >> >> > >bc >> >> > >> >> > 86400/3600 >> >> > 24 >> >> > >> >> > >> >> > Should only take a day based on the results above. >> >> > >> >> > The command to see your XM settings is >> >> > dig <url> mx >> >> >> >> Did you update the serial number when you changed the MX record? >> >> Servers downline will not see the changes otherwise. >> > >> > >> > Actually, the serial number is only used by the slave servers for a >> > particular zone to decide whether or not a zone transfer is needed. >> > >> >> I don't think that's entirely true. The serial number is also used by >> named internally to determine whether to reload your zones, and hence, >> to make the actual change in memory. AFAIK if you don't update the >> serial number the change won't take effect. >> >> To confirm this I just ran `rndc reload` and then checked >> /var/log/messages on my closest available OBSD name server. Reloaded >> named.conf but NOT my zone files. Then I changed the serial on one of my >> primary zone files and ran `rndc reload` again. This time syslog records >> that both named.conf and that zone have been reloaded. > > > Did you actually make a change to one of the zone files? or did you just > look at logs? > > If you make a change to one of the zone files without changing the > serial number, and then do rndc reload, the changes will be reflected in > queries sent to that named process. > > To quote the fourth edition of "DNS and BIND" page 432: > > "When you reload the primary, it loads the updated zone file regardless > of whether you've changed the serial number." > I stand corrected. Thanks for the clarification and reference. G
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43892897.7010507>