In article mailman.2063.1389807192.20661.bind-us...@lists.isc.org,
Warren Kumari war...@kumari.net wrote:
On Tue, Jan 14, 2014 at 12:39 PM, Blason R blaso...@gmail.com wrote:
Hi Folks,
I am not sure if this is an appropriate forum to answer since more or less
it is pertaining to Go
Hello.
I have dynamic zone. And A record in it:
Example(pseudo-code):
*zone myzone.*
* a 10.0.0.1 domain xxx*
Then I made DHCP update for host host.myzone. and it receives address
from dynamic range (10.0.0.10-10.0.0.100), for example: 10.0.0.10.
So host.myzone. has 2 A records: 10.0.0.1
On 01/15, Bill Owens wrote:
On Tue, Jan 14, 2014 at 07:55:44PM -0500, Kevin Darcy wrote:
Loopback is anti-social; an apparent attempt to make the client
waste resources connecting to itself. In legal terms, one might call
this an attractive nuisance.
You're quite right; that's why I have
Am I correct in understanding that the change to enabled by default was in
9.9.x, not in 9.8.x? The 9.9.x specifically states that is enabled by
default whereas the 9.8.x documentation does not.
-Original Message-
From: Lawrence K. Chen, P.Eng. [mailto:lkc...@ksu.edu]
Sent: Tuesday,
Sorry for the double post, but I forgot to ask this:
And if it is indeed enabled regardless of my RFC1918 ranges, I would imagine
that for my internal servers which have those ranges, I would want to add
disable-empty-zone .; to my global options? And for my external-facing
server which of course
-Original Message-
From: Mike Bernhardt bernha...@bart.gov
Date: Thursday, January 16, 2014 4:09 PM
To: bind-users@lists.isc.org bind-users@lists.isc.org
Subject: RE: Upgrading from 9.8.3 to 9.9.4
Sorry for the double post, but I forgot to ask this:
And if it is indeed enabled regardless
6 matches
Mail list logo