ailed--compilation aborted at ./bindkeys.pl line 20.
make[2]: *** [bind.keys.h] Error 2
make[2]: Leaving directory `/home/src/bind-9.7.2/bin/named'
make[1]: *** [subdirs] Error 1
make[1]: Leaving directory `/home/src/bind-9.7.2/bin'
make: *** [subdirs] Error 1
Ideas are most appreciated.
T
On Tue, Sep 28, 2010 at 6:10 PM, michael wrote:
> Hello,
>
> On Tue, Sep 28, 2010 at 6:01 PM, fakessh wrote:
>> Le mercredi 29 septembre 2010 02:34, michael a écrit :
>>> Hello,
>>>
>>> Trying to upgrade to Bind-9.7.2-P2 on an older Linux system.
>
Hello Mark,
Thanks for the reply!
I will try in a few hours --with-make-clean=no
Thanks,
Michael...
On Tue, Sep 28, 2010 at 6:47 PM, Mark Andrews wrote:
>
> In message ,
> mich
> ael writes:
>> On Tue, Sep 28, 2010 at 6:10 PM, michael wrote:
>> > Hello,
>>
Hello Mark,
On Tue, Sep 28, 2010 at 6:53 PM, michael wrote:
> Hello Mark,
>
> Thanks for the reply!
>
> I will try in a few hours --with-make-clean=no
>
> Thanks,
>
> Michael...
Success!
Thanks for the answer as well as many years of a great product!!
Michael...
E R wrote:
> I am planning on implementing the current version of BIND to replace the
> aging, undocumented authoritative servers I inherited. I want to hide the
> primary server on our internal network and have two secondary servers be
> publicly available. While reading the DN
John Thurston wrote:
> On a resolver running ISC BIND 9.16.36 with "dnssec-validation auto;" I am
> writing "category dnssec" to a log file at "severity info;" When I look
in
> the resulting log file, I'm guessing that lines like this:
> validating com/SOA: got insecure respon
Can you share a bit about why you want to get out of using
opendnssec/openhsm?
I would regard this as an opportunity to test key rollover with your parent
zone :-)
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works
Mike Lieberman wrote:
> The newer router blocks my local BIND servers (ONLY not clients using
> downstream servers) from receiving anything from the Internet. OUR BIND
> servers still have the local networks, but nothing else.
Your explanation is rather obtuse, but I think you mean t
Serg via bind-users wrote:
> As an alternative approach I have tried to run with a configuration
> "listen-on-v6 { any; }", but it does behave in a way I need - it binds
> separate socket for each discovered IP address rather wildcard address
> of [::].
Bind needs to bind a new s
m...@at.encryp.ch wrote:
> Regarding the usage of [::] - due to usage of firewall I am able to
> block connections to the 53/udp and 53/tcp which are not coming to
> specific IP addresses or ranges, I do not need such filtering
> functionality within bind itself.
Bind doesn't list
Mark Andrews wrote:
> where wrong and wouldn’t normally be that way. Something or someone
> changed them. It may have happened again. We can’t see what you see
And, AppArmor can turn things into permission denied, which are rather
mysterious. So, I'd ask for dmesg output too.
sign
e Question section empty."
There are some older implementations out there that don't do this
correctly. I have a vendor supported IPAM implementation, where I have
gone back to the vendor and quoted the above, and they have fixed the
implementation.
michael
On 8/31/23 17:34, Ian Bobb
Silva Carlos wrote:
> On server A I configured HyperLocal. On Server B I did NOT configure
> HyperLocal.
> I ran the command "dig @localhost EXAMPLES" on both servers.
> EXAMPLES: blabla.sdf.dd or teste.com.eroterrter or world.nanana
> Problem: Both Servers report that "Quer
In general, you don't want to mix dynamic update zones with ones that you
want to edit by hand. I see that you are doing manual DNSSEC signing in your
cron job.
Your choices are:
a) do everything with dynamic update, and turn on automatic DNSSEC management
in bind9.
b) do your DNSSEC signing
lves the problem if interactive. Cron running a week
later usually works)
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca/
Given VPNs, RemoteAccess and the like, I strongly recommend against split-DNS
configurations. They were great ideas in 1993, when all sites were concave,
but that's just not the case anymore.
Instead, I recommend having a sub-zone, "internal.example.com", or some other
convenient name. Put a zo
Greg Choules via bind-users wrote:
> What would be better (IMHO) is for you to keep "example.com" as your
> external zone in an external (hopefully in a DMZ) primary server,
> serving the world with public addresses they need to reach, and
> internally create a new zone - "interna
6.42/reference.html#key-statement-definition-and-usage>.
It is defined globally and should be available in all views (and the
output from tsig-list confirms this).
As this has been rejected as an error within minutes
(https://gitlab.isc.org/isc-projects/bind9/-/issues/4539) it must be a
user error.
https://bind9.readthedocs.io/en/v9.16.42/advanced.html#errors). As it
is, I was too focused on finding a problem with defining a key at all.
Maybe pointing out this would be an acceptable issue...
Thanks again!
- Michael
Am 17.01.24 um 18:26 schrieb Anand Buddhdev:
On 17/01/2024 18:18, Michael
actices. (It also provides
some level of job security :-D.)
But in this case, I think the BIND developers did a good job ensuring
there was a way to create policies that integrate well with
key-management regimes external to BIND.
michael
--
Visit https://lists.isc.org/mailman/listinfo/b
Matthijs Mekking wrote:
> As the main developer of dnssec-policy, I would like to confirm that
> what has been said by Michael and Nick are correct.
Cool.
> - When migrating to dnssec-policy, make sure the configuration matches
> your existing keys.
Is there a way
(or some level of
failure in between all queries and the ones for that one domain)? And at that
time, can you successfully query from the same system using a public resolver
(e.g. "dig @9.9.9.9 s1._domainkey.mg-esp-prod-eu-eu.mallorcazeitung.es TXT")?
And do you have BIND's
limit the amount of
information you provide to those who are trying to help you or make them infer
information. It's fine to mention only certain packets in an email, but put the
full packet capture on a public resource somewhere accessible.
Michael Batchelder
ISC Support
--
Visit https:
Thomas,
I just incorrectly wrote:
> So at minimum add "icmp and arp" to your filter expression.
I did not mean to use the logical "and". Your minimum filter should be
something like:
"src port 53 or icmp or arp"
Sorry for the confusion,
Michael
along with the BIND log segment which contains the
failed queries.
Michael Batchelder
ISC Support
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.
Mark Andrews wrote:
> Named and nsupdate validate input for types they know about (both text
> and wire). You would have to use versions that are not HTTPS aware and
> use unknown type format.
So, he could code it in Perl or Python or something which had a dynamic DNS
library. Bind
> Yes, sure. I grabbed three typical cases to analyze further, and
> currently trying to understand the proceedings - unsuccessfully, up
> to now. :(
>
> Case 1:
> ---
> Jun 19 17:42:12 conr named[24481]: lame-servers:
>info: success resolving '26.191.165.185.in-addr.arpa/PTR'
>
> Hello Michael
> Thank you for your response. Here is a pcap file and some logs.
Hello Sami,
Your pcap shows your resolver making thousands of queries that get no responses
(or at least the pcap does not contain them). There's not much I can say,
beyond that this does not app
>> Hello Michael
>> Thank you for your response. Here is a pcap file and some logs.
>
> Hello Sami,
>
> Your pcap shows your resolver making thousands of queries that get
> no responses (or at least the pcap does not contain them). There's
> not much I can say,
ng that you should upgrade).
> How can we ensure that this is a network-level issue?
Through standard network troubleshooting techniques, such as packet captures
and firewall log inspection. Beyond that, you'll need to inquire elsewhere, as
I indicated at the top of this message, as this is a list abo
On Tuesday, August 27th, 2024 at 4:21 AM, Ondřej Surý wrote:
> the Docker images have been updated to use Alpine Linux as the base image
> and the bind9 binaries are now compiled from the source while building the
> Docker images. This is more in-line with the expected Docker (Podman)
> workfl
PLEASE READ: An important security announcement from ISC
ISC has been notified by Haixin Duan (a professor at Tsinghua
University in Beijing China, who is currently visiting the
International Computer Science Institute (ICSI) at the University
of California, Berkeley) about a DNS resolve
+dnssec -t SOA org 198.41.0.4
[snip]
Your dig foo is a bit off today. Remember, to explicitly specify a name
server, you need to prepend the IP address with @. You meant to say:
dig +dnssec -t SOA org @198.41.0.4
What you ended up getting is the RRSIG for the root SOA and for the NSEC
r
be okay at looking up DS records (when asked for them)
for 2nd and 3rd level domains but not for TLDs. Based on some
experimentation with some obscure domains I own, it does seem to be
properly querying the parent. It just does the wrong thing for TLDs (at
this point).
It is a known issue, and is indeed a bug. We're working on it already, so stay
tuned.
--Michael
On Feb 14, 2012, at 12:44 PM, Alex wrote:
> Hi,
>
> I have a fedora16 x86_64 box and named keeps dying with an assertion failure:
>
> 14-Feb-2012 13:24:41.137 general: cr
Introduction
BIND 9.9.0rc3 is the third release candidate for BIND 9.9.0
This document summarizes changes from BIND 9.8 to BIND 9.9.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software can alwa
Hello,
I'm looking for advice on an issue. I have a publicly registered domain
which we also use internally. I have bind configured as a caching DNS server.
Bind is configured to use four other Windows DNS servers as forwarders for the
domain. Bind should be using the root servers for any
he root servers at step 3. Sometimes when I
perform these steps I will get the external DNS servers returned as the name
servers or in the authoritative section.
Thank you,
Mike
-Original Message-
From: Spain, Dr. Jeffry A. [mailto:spa...@countryday.net]
Sent: Tuesday, February 2
Introduction
BIND 9.9.0rc4 is the fourth release candidate for BIND 9.9.0
This document summarizes changes from BIND 9.8 to BIND 9.9.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software can alw
Introduction
BIND 9.9.0 is the first production release of BIND 9.9.
This document summarizes changes from BIND 9.8 to BIND 9.9.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software can always b
more than 4k will exceed the default settings for EDNS0 UDP responses.
If you dig @ your server, with +tcp, do you get a reply? If not, perhaps you
are not allowing TCP connections to port 53?
What error you are getting may be of help.
--Michael
On Feb 29, 2012, at 1:20 PM, Darvin Denmian
f TXT records, each at its own name like in
your example, you should not be running into problems.
--Michael
On Feb 29, 2012, at 1:48 PM, Darvin Denmian wrote:
> Hi,
>
> Graff, thanks for you reply...
>
> As you can see below my server is accepting DNS connections:
Introduction
BIND 9.6-ESV-R6rc2 is the second release candidate for BIND 9.6-ESV-R6.
This document summarizes changes from BIND 9.6-ESV-R5 to BIND
9.6-ESV-R6rc2. Please see the CHANGES file in the source code
release for a complete list of all changes. Please see the CHANGES
file in t
Introduction
BIND 9.7.5rc2 is the second release candidate for BIND 9.7.5.
This document summarizes changes from BIND 9.7.4 to BIND 9.7.5rc2.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software can
Introduction
BIND 9.8.2rc2 is the second release candidate for BIND 9.8.2.
This document summarizes changes from BIND 9.8.1 to BIND 9.8.2rc2.
Please see the CHANGES file in the source code release for a complete
list of all changes.
Download
The latest versions of BIND
Yes.
In recent versions of dig, you can use the following option, as
documented in the man page:
+[no]onesoa
Print only one (starting) SOA record when performing an
AXFR. The
default is to print both the starting and ending SOA records.
mich
n 288 ms.
SOA dcaowa01.dca.com. administrator.dubaiairport.com. 2005061961 900 600
86400 7200 from server 194.170.1.6 in 289 ms.
SOA dcaowa01.dca.com. administrator.dubaiairport.com. 2005061961 900 600
86400 7200 from server 194.170.1.7 in 293
Hello,
I'm troubleshooting a DNS issue we recently experienced where records were
unresolveable, response NXDOMAIN, from the caching DNS server. I flushed the
cache using rndc flush and I received the host's ip.
There were no errors in the system log so I'm enabling debug logging should
i
Operational Notification -- Segmentation Fault in resolver.c
Affects BIND 9.6-ESV-R6, 9.7.5, 9.8.2, & 9.9.0
Summary:
ISC has discovered a race condition in the resolver code that
can cause a recursive nameserver running BIND 9.6-ESV-R6, 9.7.5,
9.8.2, or 9.9.0 to crash with a segmentation
Some signature methods require this, some do not. RSA should not (in general)
but RSA encryption in practice may. Signing is different, in that you know
both halves (encrypted and cleartext) so it should not require padding.
I think DSA does require randomness in signing.
--Michael
On May
Introduction
BIND 9.9.1 is the latest production release of BIND 9.9.
This document summarizes changes from BIND 9.9.0 to BIND 9.9.1.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software can alw
Introduction
BIND 9.8.3 is the latest production release of BIND 9.8.
This document summarizes changes from BIND 9.8.2 to BIND 9.8.3.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software can al
Introduction
BIND 9.7.6 is the latest production release of BIND 9.7.
This document summarizes changes from BIND 9.7.5 to BIND 9.7.6.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software can alw
Introduction
BIND 9.6-ESV-R7 is the most recent release of BIND 9.6-ESV.
BIND 9.6-ESV is an Extended Support Version of BIND 9.
This document summarizes changes from BIND 9.6-ESV-R6 to BIND
9.6-ESV-R7. Please see the CHANGES file in the source code
release for a complete list of
ut or BIND itself to swap.
75% or 85% range seems like a good starting point.
--Michael
On May 31, 2012, at 8:18 PM, Doug Barton wrote:
> On 5/31/2012 1:51 PM, blrmaani wrote:
>
>> Question:
>> what is the recommended configuration for 'max-cache-size' for optimum
>&g
Technically, BIND 9 could run with a very, very small cache. The
default of 32 MB is actually a fairly new thing. It used to be unlimited, but
that means BIND will hit some operating system imposed limit, and that is more
painful than self-management.
--Michael
On Jun 1, 2012, at 12:26
Introduction
BIND 9.7.6-P1 is the latest production release of BIND 9.7.
This document summarizes changes from BIND 9.7.5 to BIND 9.7.6-P1.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software c
Introduction
BIND 9.9.1-P1 is the latest production release of BIND 9.9.
This document summarizes changes from BIND 9.9.0 to BIND 9.9.1-P1.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software c
Introduction
BIND 9.8.3-P1 is the latest production release of BIND 9.8.
This document summarizes changes from BIND 9.8.2 to BIND 9.8.3-P1.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software c
Introduction
BIND 9.6-ESV-R7-P1 is the most recent release of BIND 9.6-ESV.
BIND 9.6-ESV is an Extended Support Version of BIND 9.
This document summarizes changes from BIND 9.6-ESV-R6 to BIND
9.6-ESV-R7-P1. Please see the CHANGES file in the source code
release for a complete li
On Tue, 5 Jun 2012, Manson, John wrote:
Will bind run on VMware?
Yes. I have a few machines running BIND 9.9.x on FreeBSD as a guest os on
vmware.
michael
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from
it reaches the maximum too quickly, add more cache size.
I suspect this is one metric that would help greatly to add to the XML stats...
Cache hit rate is sort of a standard metric.
--Michael
___
Please visit https://lists.isc.org/mailman/listinfo/bi
the new set,
99.% of the world will be good.
The case exists where oldprovider.net's users (say, mail servers, etc) may
continue using their copy of the zone. However, I doubt you care overly much
about that unless oldprovider.net is huge.
--Michael
On Jun 18, 2012, at 8:
wever, anything
else that is currently depending on the openssl shared library from
ports (as opposed to the bundled system) will need to be recompiled
before it will work, as will bind 9.8.
Doug Barton may have some better ideas as to how best to make it all work.
mi
Introduction
BIND 9.7.7b1 is the first beta release of BIND 9.7.7
This document summarizes changes from BIND 9.7.6 to BIND 9.7.7b1.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software can always be
Introduction
BIND 9.8.4b1 is the first beta release of BIND 9.8.4
This document summarizes changes from BIND 9.8.3 to BIND 9.8.4b1.
Please see the CHANGES file in the source code release for a
complete list of all changes. Download
The latest versions of BIND 9 software can always be
Introduction
BIND 9.6-ESV-R8b1 is the first beta release of BIND 9.6-ESV-R8.
BIND 9.6-ESV is an Extended Support Version of BIND.
This document summarizes changes from BIND 9.6-ESV-R7 to BIND
9.6-ESV-R8b1. Please see the CHANGES file in the source code
release for a complete list of a
Introduction
BIND 9.9.2b1 is the first beta release of BIND 9.9.2.
This document summarizes changes from BIND 9.9.1 to BIND 9.9.2b1.
Please see the CHANGES file in the source code release for a
complete list of all changes. Download
The latest versions of BIND 9 software can always be
Introduction
BIND 9.9.2rc1 is the first release candidate of BIND 9.9.2.
This document summarizes changes from BIND 9.9.1 to BIND 9.9.2rc1.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software c
Introduction
BIND 9.8.4rc1 is the first release candidate of BIND 9.8.4
This document summarizes changes from BIND 9.8.3 to BIND 9.8.4rc1.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software ca
Introduction
BIND 9.6-ESV-R8rc1 is the first release candidate of BIND
9.6-ESV-R8.
BIND 9.6-ESV is an Extended Support Version of BIND.
This document summarizes changes from BIND 9.6-ESV-R7 to BIND
9.6-ESV-R8rc1. Please see the CHANGES file in the source code
release for a com
Introduction
BIND 9.7.7rc1 is the first release candidate of BIND 9.7.7
This document summarizes changes from BIND 9.7.6 to BIND 9.7.7rc1.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software c
Introduction
BIND 9.9.1-P3 is the latest production release of BIND 9.9.
This document summarizes changes from BIND 9.9.0 to BIND 9.9.1-P3.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software c
Introduction
BIND 9.6-ESV-R7-P3 is the latest production release of BIND
9.6-ESV.
BIND 9.6-ESV is an Extended Support Version of BIND 9.
This document summarizes changes from BIND 9.6-ESV-R6 to BIND
9.6-ESV-R7-P3. Please see the CHANGES file in the source code
release for a co
Introduction
BIND 9.7.6-P3 is the latest production release of BIND 9.7.
This document summarizes changes from BIND 9.7.5 to BIND 9.7.6-P3.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software c
Introduction
BIND 9.8.3-P3 is the latest production release of BIND 9.8.
This document summarizes changes from BIND 9.8.2 to BIND 9.8.3-P3.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software c
Note:
This email advisory is provided for your information. The most
up to date advisory information will always be at:
https://kb.isc.org/article/AA-00778 please use this URL for the
most up to date advisory information.
---
CVE-2012-4244: A specially crafted Resource Record could cause
On 9/13/12 2:01 AM, pangj wrote:
> Should we use the latest 9.9 version of BIND instead of others 9.x?
At the current moment, ISC develops and provides patches for four
different version sequences of BIND 9:
BIND 9.6-ESV
BIND 9.7
BIND 9.8
& BIND 9.9
They are intended to serve slightly di
On 9/13/12 3:03 PM, Michael McNally wrote:
BIND 9.8 will be the next version to become an Extended Support Version
and will be supported for several years hence. BIND 9.8 is stable,
reasonably mature, and will be supported with some feature improvements
and all bug fixes.
I erred when
incentive to get things right and fix
them quickly. At UC Berkeley, validation has been turned on for four
years now and only a handful of domains have required "special handling."
All of the emphasis on signing for DNSSEC is great, but DNSSEC can't
really work without validation.
cle/AA-00804
Michael McNally
ISC Support
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
On 9/28/12 9:38 AM, Michael McNally wrote:
Empty zone behavior has changed in 9.9, and the 10.0.0.0/8 zone
is part of the changes.
You can find a good explanation of the differences in this ISC
Knowledge Base article:
https://deepthought.isc.org/article/AA-00804
Oh drat -- that'
Introduction
BIND 9.7.7 is the latest production release of BIND 9.7.
This document summarizes changes from BIND 9.7.6 to BIND 9.7.7.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software can alw
Introduction
BIND 9.9.2 is the latest production release of BIND 9.9.
This document summarizes changes from BIND 9.9.1 to BIND 9.9.2.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software can alw
Introduction
BIND 9.9.1-P4 is the latest production release of BIND 9.9.1 (BIND
9.9.2 is also available for download and is the latest production
release of BIND 9.9).
This document summarizes changes from BIND 9.9.0 to BIND 9.9.1-P4.
Please see the CHANGES file in the source code
Introduction
BIND 9.8.3-P4 is the latest production release of BIND 9.8.3 (BIND
9.8.4 is also available for download and is the latest production
release of BIND 9.8).
This document summarizes changes from BIND 9.8.2 to BIND 9.8.3-P4.
Please see the CHANGES file in the source code
Introduction
BIND 9.7.6-P4 is the latest production release of BIND 9.7.6 (BIND
9.7.7 is also available for download, and is the latest production
release of BIND 9.7).
This document summarizes changes from BIND 9.7.5 to BIND 9.7.6-P4.
Please see the CHANGES file in the source code
9.6-ESV-R8
9.7.7
9.8.4
9.9.2
Michael McNally
ISC Support
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
CVE-2012-5166: Specially crafted DNS data can cause a lockup in named
A nameserver can be locked up if it can be induced to load a specially
crafted combination of resource records.
CVE: CVE-2012-5166
Document Version: 2.0
Posting date: 9 October 2012
Program Impacted: BIND
Versions affe
Introduction
BIND 9.8.4 is the latest production release of BIND 9.8.
This document summarizes changes from BIND 9.8.3 to BIND 9.8.4.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software can alw
Introduction
BIND 9.6-ESV-R7-P4 is the latest production release of BIND
9.6-ESV-R7 (BIND 9.6-ESV-R8 is also available for download, and is
the latest production release of BIND 9.6-ESV).
BIND 9.6-ESV is an Extended Support Version of BIND 9.
This document summarizes changes from
Introduction
BIND 9.6-ESV-R8 is the latest production release of BIND 9.6-ESV.
BIND 9.6-ESV is an Extended Support Version of BIND.
This document summarizes changes from BIND 9.6-ESV-R7 to BIND
9.6-ESV-R8. Please see the CHANGES file in the source code release
for a complete list
e.
>
> Here's a brief survey <http://www.surveymonkey.com/s/2VYNKWR> for
> Schools that have ISC running in an AD environment.
>
> http://www.surveymonkey.com/s/2VYNKWR
Done, on behalf of the "other" Berkeley. :)
michael
___
A specific query can cause BIND nameservers using DNS64 to exit with a REQUIRE
assertion failure.
CVE: CVE-2012-5688
Document Version:2.0
Posting date:04 Dec 2012
Program Impacted:BIND
Versions affected: 9.8.0->9.8.4, 9.9.0->9.9.2
Severity:
Introduction
BIND 9.9.2-P1 is a security-fix release, superceding BIND 9.9.2
as the latest production release of BIND 9.9.
This document summarizes changes from BIND 9.9.1 to BIND 9.9.2-P1.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Introduction
BIND 9.8.4-P1 is a security-fix release, superceding BIND 9.8.4
as the latest production release of BIND 9.8.
This document summarizes changes from BIND 9.8.3 to BIND 9.8.4-P1.
Please see the CHANGES file in the source code release for a
complete list of all changes.
ISC has learned of the potential for an error condition in BIND 9
that can cause a nameserver to terminate with an assertion failure
when processing queries if it has been configured to use both DNS64
and Response Policy Zones (RPZ).
CVE: CVE-2012-5689
Document Version: 2.0
Introduction
BIND 9.8.5b1 is the first beta release of BIND 9.8.5
This document summarizes changes from BIND 9.8.4 to BIND 9.8.5b1.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software can alway
Introduction
BIND 9.9.3b1 is the first beta release of BIND 9.9.3.
This document summarizes changes from BIND 9.9.2 to BIND 9.9.3b1.
Please see the CHANGES file in the source code release for a
complete list of all changes.
Download
The latest versions of BIND 9 software can alwa
Introduction
BIND 9.6-ESV-R9b1 is the first beta release of BIND 9.6-ESV-R9.
BIND 9.6-ESV is an Extended Support Version of BIND.
This document summarizes changes from BIND 9.6-ESV-R8 to BIND
9.6-ESV-R9b1. Please see the CHANGES file in the source code
release for a complete list
1 - 100 of 489 matches
Mail list logo
