On Nov 17, 2011, at 6:28 PM, Mark Andrews wrote:
In message 20171600.pahg0ucw011...@scramble.princeton.edu, Irwin
Tillman writes:
It appears that named is trying to use ports I've mentioned in
avoid-v4-udp-ports.
Platform: BIND 9.8.1-P1 on Solaris 10 / SPARC
On some of the ports
On Jun 24, 2011, at 3:33 PM, Phil Mayers wrote:
On 06/24/2011 06:39 PM, David Coulthart wrote:
configure the zone as forward first, the recursive nameserver gets
back the NS delegation then uses that to perform an iterative query
against the authoritative nameserver for the subdomain
Currently the two recursive caching nameservers for clients on our network are
also authoritative for a few zones. In particular, they are authoritative for:
1) our main forward zone (columbia.edu) in order to provide an internal view of
the zone
2) RFC 1918 reverse zones (e.g.,
On Mar 7, 2011, at 12:24 PM, David Coulthart wrote:
On Mar 7, 2011, at 11:42 AM, Chris Thompson wrote:
On Mar 7 2011, David Coulthart wrote:
BIND Version: 9.7.3 on Solaris 9 10 (locally compiled)
...
Based on the ARM a posting to bind-users[1], I enabled
ixfr-from-differences
master
On Mar 8, 2011, at 3:44 PM, Mark Andrews wrote:
In message b840935f-4809-40cf-98c5-029cbbab4...@columbia.edu, David
Coulthart
writes:
It looks like the problem is with setting ixfr-from-differences to master. I
f I instead set the option to yes, a journal file is generated IXFR works c
BIND Version: 9.7.3 on Solaris 9 10 (locally compiled)
Our current workflow for managing DNS involves generating master zone files
from a database, pushing the new files to a hidden master nameserver then
running rndc reload on that nameserver.
Based on the ARM a posting to bind-users[1], I
On Mar 7, 2011, at 11:42 AM, Chris Thompson wrote:
On Mar 7 2011, David Coulthart wrote:
BIND Version: 9.7.3 on Solaris 9 10 (locally compiled)
Our current workflow for managing DNS involves generating master zone
files from a database, pushing the new files to a hidden master nameserver
On Feb 22, 2011, at 3:55 PM, Larissa Shapiro wrote:
Description and Impact:
When an authoritative server processes a successful IXFR transfer or a
dynamic update, there is a small window of time during which the IXFR/update
coupled with a query may cause a deadlock to occur. This deadlock
On Jan 19, 2010, at 12:28 PM, Evan Hunt wrote:
BIND 9.6.1-P3 is a SECURITY PATCH for BIND 9.6.1. It addresses two
potential cache poisoning vulnerabilities, both of which could allow
a validating recursive nameserver to cache data which had not been
authenticated or was invalid.
Do these
9 matches
Mail list logo
