El mar, 15-09-2009 a las 17:27 -0400, Robert Spangler escribió:
> On Tuesday 15 September 2009 08:16, Frank Stanek wrote:
>
> > Please forgive my naivety if this is totally wrong but
> > I don't have a chrooted bind environment to verify this atm.
>
> I run a chroot environment
>
> > But does
Don't think TSIG Key roll-over is possible - in the DNSSEC sense. Don't
think it is as necessary either. I have separate TSIG relationships
between my Primary and Secondary peers. I use the same TSIG for all
zones that are on both peers - the TSIG is to secure the path between
the two peers. I also
In message <4ab072dc.2070...@nzrs.net.nz>, Sebastian Castro writes:
> Hi everyone:
>
> I was reading the document "Deprecation of HMAC-MD5 in DNS TSIG and TKEY
> Resource Records"
> (http://www.ietf.org/id/draft-ietf-dnsext-tsig-md5-deprecated-03.txt)
> and I thought "Darn, I must be prepared to
Hi everyone:
I was reading the document "Deprecation of HMAC-MD5 in DNS TSIG and TKEY
Resource Records"
(http://www.ietf.org/id/draft-ietf-dnsext-tsig-md5-deprecated-03.txt)
and I thought "Darn, I must be prepared to do a TSIG renovation", so
started researching how to do it.
First step was check
--- Blind-Carbon-Copy
To: bind-annou...@isc.org
From: Mark Andrews
Subject: BIND 9.5.2rc1 is now available.
Date: Wed, 16 Sep 2009 14:45:09 +1000
Sender: ma...@drugs.dv.isc.org
BIND 9.5.2rc1 is now available.
BIND 9.5.2rc1 is a maintenance release candidate for BIND
On Tuesday 15 September 2009 08:16, Frank Stanek wrote:
> Please forgive my naivety if this is totally wrong but
> I don't have a chrooted bind environment to verify this atm.
I run a chroot environment
> But doesn't the init script in some distributions copy the
> configuration files (inclu
BIND 9.7.0a3 is now available.
BIND 9.7.0a3 is the third alpha release of BIND 9.7.0.
Overview:
This is a technology preview of new functionality to be
included in BIND 9.7.0. Not all new functionality is in
place. APIs and configuration sy
Hi,
Besides incrementing the serial, be sure there are no syntactical errors in the
zone file. Easiest way is to check your logs or use named-checkzone to validate
the file. Your logs should show something regardless. "rndc reload "
should return either "zone reload queued" or "zone reload up-t
Udo Zumdick wrote:
One other way I know is to use Dynamic DNS, but it is more complicated and
(in my opinion) also sort of unsecure.
Isn't that kind of like saying modifying a file is "sort of unsecure"?
You don't let random people modify your files without proper
protections/permissions/p
Marcos Lorenzo de Santiago schrieb:
> El mar, 15-09-2009 a las 11:50 +0100, Cathy Almond escribió:
>> Marcos Lorenzo de Santiago wrote:
>>> El mar, 15-09-2009 a las 07:04 -0300, Leonardo Rodrigues escribió:
Marcos Lorenzo de Santiago escreveu:
> When I modify a RR or add a new one on an ex
El mar, 15-09-2009 a las 11:50 +0100, Cathy Almond escribió:
> Marcos Lorenzo de Santiago wrote:
> > El mar, 15-09-2009 a las 07:04 -0300, Leonardo Rodrigues escribió:
> >> Marcos Lorenzo de Santiago escreveu:
> >>> When I modify a RR or add a new one on an existing zone, I have to
> >>> restart ma
In message <4aaf7181.4040...@isc.org>, Cathy Almond writes:
> Marcos Lorenzo de Santiago wrote:
> > El mar, 15-09-2009 a las 07:04 -0300, Leonardo Rodrigues escribi=F3:
> >> Marcos Lorenzo de Santiago escreveu:
> >>> When I modify a RR or add a new one on an existing zone, I have to
> >>> restart
Am Tue, 15 Sep 2009 12:28:24 +0200
schrieb Marcos Lorenzo de Santiago :
[]
> After making changes to zone, updated serial, and rndc reload, I dig my
> zone and get always the old serial. The serial and the changes only
> appear when I '/etc/init.d/bind restart' it.
>
> I use bind 9.5.1 on deb
Marcos Lorenzo de Santiago wrote:
> El mar, 15-09-2009 a las 07:04 -0300, Leonardo Rodrigues escribió:
>> Marcos Lorenzo de Santiago escreveu:
>>> When I modify a RR or add a new one on an existing zone, I have to
>>> restart master server to make the change available. Is there any other
>>> way to
El mar, 15-09-2009 a las 07:04 -0300, Leonardo Rodrigues escribió:
> Marcos Lorenzo de Santiago escreveu:
> > When I modify a RR or add a new one on an existing zone, I have to
> > restart master server to make the change available. Is there any other
> > way to reload the zone without stopping bin
Hi Marcos,
rndc reload should do the job, but only if the serial in that zone has been
increased.
One other way I know is to use Dynamic DNS, but it is more complicated and
(in my opinion) also sort of unsecure.
Regards,
Udo
_|_|_|_|_|_| Udo Zumdick
___ _| _ Deut
Marcos Lorenzo de Santiago escreveu:
When I modify a RR or add a new one on an existing zone, I have to
restart master server to make the change available. Is there any other
way to reload the zone without stopping bind?
I've tried with:
- rdnc reload [zone]
- rndc reconfig [zone
This is another quite short and simple question:
When I modify a RR or add a new one on an existing zone, I have to
restart master server to make the change available. Is there any other
way to reload the zone without stopping bind?
I've tried with:
- rdnc reload [zone]
- rndc rec
18 matches
Mail list logo