Index: [Article Count Order] [Thread]

Date:  Wed, 24 Oct 2007 07:52:50 +0200
From:  =?ISO-8859-1?Q?Ren=E9_M=F8lsted?= <molsted (at mark) iweb.dk>
Subject:  [coba-e:10947] Re: DNS Question
To:  coba-e (at mark) bluequartz.org
Message-Id:  <2477D28A-224D-468F-BEAD-9C161621122D (at mark) iweb.dk>
In-Reply-To:  <034201c815b5$459844d0$0601a8c0@systemax>
References:  <034201c815b5$459844d0$0601a8c0@systemax>
X-Mail-Count: 10947


On 23/10/2007, at 22.42, Gerald Waugh wrote:

> But, the slave (secondary), needs to have a named.conf (local)
> Which will accept the domains' DNS.
> So not sure your solution will work... I could be WRONG

I'm aware of that named.conf should reside on the slave, that could  
easily be done with rsync. Then do a md5 check on the new file  
against the existing to test if bind needs to be restarted.

Another approach would be to use a sql-based dns (powerdns, mydns  
etc.), that would be nice to have integrated with BQ, preferably with  
replicated sql-servers.

-- 
Rene