I will take this opportunity now to point out that upgrading to 9.9.X from any
release prior to it might cause problems if you have any slave zones. 9.9.X by
default saves slave zone files using "masterfile-format raw;", and 9.8.X and
earlier defaults to "masterfile-format text;".
It's easy to
On Mar 7, 2012, at 6:23 PM, Mark Andrews wrote:
> Compile in +sigchase support and give it a root key.
Evan Hunt told us (regarding +sigchase) "in its current state it's terrible and
you really shouldn't use it."
I'm not sure who to believe.
> TCP has *never* been optional for DNS. Unfortunat
That's a little more output, but when you try it, notice that there's no "dig
org. DNSKEY" in the output, which is the query that was hanging in my case.
On Mar 6, 2012, at 9:10 PM, Mark Andrews wrote:
>
> dig +trace +qr +comment +question
>
> --
> Mark Andrews, ISC
> 1 Seymour St., Dun
Hi, fellow BIND users.
The other day I was attempting to diagnose a problem on a recursive resolving
name server. I had just enabled DNSSEC Validation, and certain digs (such as
"www.isc.org", "www.dnssec-failed.org") were failing. Even queries to
non-signed domains such my own personal domai
On Jan 10, 2012, at 5:53 PM, Doug Barton wrote:
> On 01/10/2012 17:34, Mark K. Pettit wrote:
>> In my environment (FreeBSD) we've worked around this problem (just recently,
>> in fact), and I can provide more details if there's any interest.
>
> well I'm
There are some caveats to trying to use "interface-interval" to pick up new
IPs. If your BIND drops privileges (e.g., by using the "-u" command-line
option to named), you might have a problem getting BIND to bind() to the new IP
addresses.
For example, on FreeBSD if you use "-u" to drop privil
Not sure where to report this, but there's a problem in the documentation of
BIND 9.7.4, as distributed by ISC.
The Release Notes included in the bind-9.7.4 tarball, as well as the release
notes on the web site:
ftp://ftp.isc.org/isc/bind9/9.7.4/RELEASE-NOTES-BIND-9.7.4.html
state that the e
On Aug 8, 2011, at 1:50 PM, Chris Thompson wrote:
> On Aug 8 2011, Mark K. Pettit wrote:
>
>> My resolvers, running BIND 9.7.3P3, are having a difficult time resolving
>> the MX record for the zone "epza.gov.tw.".
>>
> [...]
>>
>> Any idea why
My resolvers, running BIND 9.7.3P3, are having a difficult time resolving the
MX record for the zone "epza.gov.tw.".
When I run "dig +trace", this is the response I get:
$ dig +trace epza.gov.tw. mx
; <<>> DiG 9.7.3-P3 <<>> +trace epza.gov.tw. mx
;; global options: +cmd
.
One of the things that got us is we didn't know BIND 8 automatically created
delegation records in a zone at the zone cut, if the nameserver knew of the
existence of the cut.
For example, if we have the following zones in our named.conf:
zone "example.com" { ... };
zone "sub.example.com" {
10 matches
Mail list logo
