On Thu, Aug 06, 2009 at 05:00:59PM -0400, Alexandre Racine wrote:
> @Justin, you mean like a 3rd DNS server? I was thinking about that
> since one recent RFC recommend that 3 DNS servers within 3 networks
> should be present (primary, secondary, and third).
Not for the same reason as having 2 or 3
On Thu, Aug 06, 2009 at 04:06:23PM -0400, Kevin Darcy wrote:
> For good measure, you should probably also set yourself up to slave
> 25.70.in-addr.arpa from Bell Canada so that you can still resolve your
> own PTRs even if your link is down.
And (per rfc) ask if Bell will slave your delegated z
On Fri, Jul 10, 2009 at 09:44:51AM +1000, Mark Andrews wrote:
> You should make your servers stealth slaves for 22.206.193.in-addr.arpa
And the parent server should be a slave for the delegated zone.
RFC 2317 section 5.1
http://www.dns.net/dnsrd/rfc/rfc2317.html
Justin
__
On Mon, Nov 17, 2008 at 09:38:13PM -0600, root net wrote:
> I have a server I am testing before I put in production. Working on a more
> secure bind config. BTW if anyone has any other suggestions on locking down
> bind beside below and chroot let me know.
Use TSIG for master-slave communication,
4 matches
Mail list logo
