Date: Fri, 29 Sep 95 00:58 PDT From: pete@puffin.pelican.com (Pete Carah) To: shorty@iii.net Cc: questions@freebsd.org Subject: Re: option GATEWAY and DNS Message-ID: <m0syaKn-0000S2C@puffin.pelican.com> In-Reply-To: <199509290037.UAA02268@iii1.iii.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199509290037.UAA02268@iii1.iii.net> you write: ... >Second question, >I used to have the DNS for my domain down by my service provider, and now I'm >going to be running named myself as the primary server. If originally my server >was nic.iii.net primary and beatnic.iii.net secondary and now I'll have >scds1.scds.com primary and nic.iii.net secondary how do I need to edit my zone >file? (that's where I have all of the commands defining node names, mail servers, etc...). Do this in two steps. First set up named with your system secondary and the current primary's ip address in named.boot as the primary. Second, start named (or kill -HUP it) and wait till named sucks up the secondary file (should only be a few seconds). Now edit named.boot to make that file primary and kill -HUP the server, and notify your current primary to make himself secondary and you primary. One thing you *don't* want is for both of you to be secondary at the same time for very long... Both primary is OK as long as the records are mostly the same. (it is a bad idea to make changes during this transition). Also the external world can't tell who is acting as primary or secondary; I'm actually primary for one domain with the internic not pointing to me at all; it only points to 2 secondaries. (this isn't recommended by any of the manuals, but it can be a handy configuration) >Also do I need to update the one on my secondary server when I update mine, or >is it automatic? If the times in the SOA are reasonable *and* you remember to update the SOA serial number whenever you update any contents (I forget remarkably often :-(, then (and only then) it is automatic. Since I can login as root on most of my secondaries I will sometimes force matters by logging in there and doing an extra kill -HUP of named (which works for this purpose in 2.x but *not* in 1.1.5; I don't know about Sun or other commercial versions of named but there's a good chance of them acting like our 1.1.5; in that case you either have to delete the zone file then do the kill -HUP or sometimes even to stop and restart named. (or just wait out the refresh time and let the process be automatic (if slow) the way it was intended.)) >last question is how do I make sure that my server returns the >addresses for machines not in my domain properly? As long as your root.cache is reasonable and you don't start named with the -r flag all should be automatic (also presuming you're not behind a firewall). -- Pete
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0syaKn-0000S2C>