In article <[email protected]>, Dave Filchak <[email protected]> wrote:
> I was thinking that as well ... would probably be the easiest and then > switch it back later. However, I would have to change my glue record at > the registrar as well ... no? The glue records don't distinguish between masters and slaves. But it would be a good idea to remove a server from delegation if it's not going to respond. > > On 06/05/10 11:19 PM, Barry Margolin wrote: > > In article<[email protected]>, > > Bruce Ray<[email protected]> wrote: > > > > > >> You have until the expiry counter expires for a given zone. > >> > >> We typically run our expiries at a week to allow for this type of failure. > >> > > You can easily turn a slave into a master. Just go into its named.conf > > file, change "type slave" to "type master" and comment out the "masters > > {...}" clause. > > > > > >> ________________________________ > >> From: [email protected] > >> <[email protected]> > >> To: [email protected]<[email protected]> > >> Sent: Thu May 06 21:37:35 2010 > >> Subject: Master server offline > >> > >> Our master server machine had a drive failure and looks like it will be > >> offline for some time. Somewhere in the back of my mind, I thought I > >> remembered that something bad can happen to the dns resolution for your > >> zones > >> if the master is offline for too long. Is there anything to this or am I > >> just > >> dreaming? As long as the secondary can answer request, we should be ok? > >> > >> Cheers, > >> > >> Dave > >> > > -- Barry Margolin, [email protected] Arlington, MA *** PLEASE don't copy me on replies, I'll read them in the group *** _______________________________________________ bind-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/bind-users
