HI ,
How to sign a zone for getting NSEC3, NSEC3PARAM RR's in a signed zone.
Thanks Regards,
Ramesh
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Not quite the right place to report this but...
wget http://ftp.isc.org/isc/bind9/9.7.0-P1/bind-9.7.0-P1.tar.gz
--2010-05-06 10:53:30--
http://ftp.isc.org/isc/bind9/9.7.0-P1/bind-9.7.0-P1.tar.gz
Resolving ftp.isc.org... 204.152.184.110, 2001:4f8:0:2::18
Connecting to
Acouple people have pointed out that I am attempting to connect to
ftp.isc.orgftp://ftp.isc.org
using http.
That is so, but that is what happens if you use the download links on
www.isc.orghttp://www.isc.org
if you click on the web
And it is back now.
wget http://ftp.isc.org/isc/bind9/9.7.0-P1/bind-9.7.0-P1.tar.gz
--2010-05-06 11:06:48--
http://ftp.isc.org/isc/bind9/9.7.0-P1/bind-9.7.0-P1.tar.gz
Resolving ftp.isc.org... 204.152.184.110, 2001:4f8:0:2::18
Connecting to ftp.isc.org|204.152.184.110|:80... connected.
HTTP
Not quite the right place to report this but…
wget http://ftp.isc.org/isc/bind9/9.7.0-P1/bind-9.7.0-P1.tar.gz
--2010-05-06 10:53:30--
http://ftp.isc.org/isc/bind9/9.7.0-P1/bind-9.7.0-P1.tar.gz
Resolving ftp.isc.org... 204.152.184.110, 2001:4f8:0:2::18
Connecting to
from isc.org:
ISC experienced a fiber outage this morning that affected some of our
services. It has now been fixed and you should be able to reach all of
the download servers.
___
bind-users mailing list
bind-users@lists.isc.org
They can't fool us - we know it was caused by the J server DNSSEC issue.
:-)
-Original Message-
From: bind-users-bounces+jlightner=water@lists.isc.org
[mailto:bind-users-bounces+jlightner=water@lists.isc.org] On Behalf
Of Jack Tavares
Sent: Thursday, May 06, 2010 2:17 PM
To:
On 05/06/10 13:27, Lightner, Jeff wrote:
They can't fool us - we know it was caused by the J server DNSSEC issue.
Damn that DNSSEC!!! :-D
--
Peter Laws / N5UWY
National Weather Center / Network Operations Center
University of Oklahoma Information Technology
pl...@ou.edu
Hi,
I integrated the lwresd library files into my software which in the end runs as
a process side by side with the lwresd daemon on the same machine.
I send gethostbyname messages from my process to lwresd daemon.
When I start the lwresd
There was a fibre cut in the Bay area.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
___
bind-users mailing list
bind-users@lists.isc.org
X-zuka-RWMailScanner-ID: 57AA9638001.AE218
X-zuka-rw-MailScanner-Information: Please contact the ISP for more information
Received: from Magnolia.local (unknown [70.48.209.168])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
You have until the expiry counter expires for a given zone.
We typically run our expiries at a week to allow for this type of failure.
From: bind-users-bounces+bruce.ray=zionsbancorp@lists.isc.org
bind-users-bounces+bruce.ray=zionsbancorp@lists.isc.org
Actually speaking without thinking is bad.
It's the expire timer in the SOA not the refresh.
On Thu, May 6, 2010 at 10:37 PM, Dave Filchak sub...@zuka.net wrote:
Our master server machine had a drive failure and looks like it will be
offline for some time. Somewhere in the back of my mind,
If your secondaries can't reach the primary for the period of time you have
in your SOAs for refresh the secondaries wills top answering.
--
-Ben Croswell
On Thu, May 6, 2010 at 10:37 PM, Dave Filchak sub...@zuka.net wrote:
Our master server machine had a drive failure and looks like it will
On Thu, 2010-05-06 at 22:37 -0400, Dave Filchak wrote:
Our master server machine had a drive failure and looks like it will
be offline for some time. Somewhere in the back of my mind, I thought
I remembered that something bad can happen to the dns resolution for
your zones if the master is
X-zuka-RWMailScanner-ID: A075B638001.ABE87
X-zuka-rw-MailScanner-Information: Please contact the ISP for more information
Received: from Magnolia.local (unknown [70.48.209.168])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
X-zuka-RWMailScanner-ID: 063F2638001.AC137
X-zuka-rw-MailScanner-Information: Please contact the ISP for more information
Received: from Magnolia.local (unknown [70.48.209.168])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
Secondaries need to 'know' that this old sec is now a master as well.
DNS is kind of critical (unless your internet presence is not important), so
... Knowing nothing about you org... Would rec that you priortise fixing DNS
pretty highly.
--
-___
David Miller
In article mailman.1421.1273202620.21153.bind-us...@lists.isc.org,
Dave Filchak sub...@zuka.net wrote:
I was thinking that as well ... would probably be the easiest and then
switch it back later. However, I would have to change my glue record at
the registrar as well ... no?
The glue
Please fix your mail scanner. It is breaking the headers into two
parts by inserting a blank line (see below). This makes it very
hard to reply to you.
X-zuka-RWMailScanner-Watermark: 1273807139.93...@anxgbaayeoqp7eoxtwe51g
X-zuka-RWMailScanner-From: sub...@zuka.net
X-zuka-RWMailScanner-ID:
Dave, You are missing the X in the -zuka-rw-MailScanner: Found to be
clean line.
and it appears to not match the other X-zuka-RWMailScanner headers, this
may lead to problems, and no doubt if you --lint mailscanner it will
throw errors saying mismatch for SA.
On Fri, 2010-05-07 at 13:47 +1000,
21 matches
Mail list logo
