On Fri, 2012-02-17 at 07:11 -0800, Chris Buxton wrote:
> Yes, it's quite possible to split named.conf into separate per-zone .conf
> files and then 'include' them back into named.conf. You can even put the list
> of include statements in a separate file, and then include that into
> named.conf.
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
+1 to all of Chris' suggestions, especially the bit about including one
file in named.conf, and including the per-zone files in that file. Makes
it much easier to update that file with a script, or what have you.
hth,
Doug
On 02/17/2012 07:11, Chris Buxton wrote:
> Yes, it's quite possible to
dE . wrote:
> Firstly, where do we get the public key for the DS records?
A zone's DNSKEY RRset contains its public keys, and these are hashed to
make its DS records. For example,
$ dig +nottl +noall +answer DS isc.org | perl -pe 's/\s+(?!$)/ /g'
isc.org. IN DS 12892 5 1 982113D08B4C6A1D9F6AEE1
On 2/17/12 11:35 AM, "Anand Buddhdev" wrote:
> Gaurav,
>> I want to know how AKAMAI works
> First of all, don't use so many question marks; one is enough. And use
> it only if you're actually asking a question, not when stating something.
No one reads RFC 1855 anymore. ;-)
>> May be this is
On 17/02/2012 20:15, Gaurav kansal wrote:
Gaurav,
> I want to know how AKAMAI works
First of all, don't use so many question marks; one is enough. And use
it only if you're actually asking a question, not when stating something.
> May be this is not the right forum to ask but I am asking th
-Original Message-
From: Chuck Swiger [mailto:cswi...@mac.com]
Sent: Saturday, February 18, 2012 1:04 AM
To: Gaurav kansal
Cc: bind-users@lists.isc.org
Subject: Re: Query Regarding AKAMAI Working Model
Hi, Gaurav--
On Feb 17, 2012, at 11:15 AM, Gaurav kansal wrote:
> I want
Hi, Gaurav--
On Feb 17, 2012, at 11:15 AM, Gaurav kansal wrote:
> I want to know how AKAMAI works
They work well. :-)
> May be this is not the right forum to ask but I am asking this here because
> AKAMAI heavily depend on its HL-DNS and LL-DNS AND these DNS Servers answer
> the query ba
-Original Message-
From: bind-users-bounces+gaurav.kansal=nic...@lists.isc.org
[mailto:bind-users-bounces+gaurav.kansal=nic...@lists.isc.org] On Behalf Of
Miek Gieben
Sent: Saturday, February 18, 2012 12:42 AM
To: bind-users@lists.isc.org
Subject: Re: A few conceptual question about
Dear Team,
I want to know how AKAMAI works
May be this is not the right forum to ask but I am asking this here because
AKAMAI heavily depend on its HL-DNS and LL-DNS AND these DNS Servers answer
the query based on some input it gets
from BGP Routes.
If anyone can help me then I will
[ Quoting at 00:36 on Feb 18 in "RE: A few
conceptual..." ]
> Firstly, where do we get the public key for the DS records?
>
> Can you clarify your question???
>
>
>
> Second, why do I get multiple DS records as response? –
>
> You will always get a 2 DS Records in response. One for SHA-1 and
Firstly, where do we get the public key for the DS records?
Can you clarify your question???
Second, why do I get multiple DS records as response? -
You will always get a 2 DS Records in response. One for SHA-1 and second for
SHA-256.
_
dig +dnssec -t DS isc.org @b0.org.afilia
Firstly, where do we get the public key for the DS records?
Second, why do I get multiple DS records as response? --
dig +dnssec -t DS isc.org @b0.org.afilias-nst.org.
; <<>> DiG 9.8.1 <<>> +dnssec -t DS isc.org @b0.org.afi
On 2/4/2012 12:36 PM, Spain, Dr. Jeffry A. wrote:
> The BIND9.9.0rc2.zip Windows installer allows for a “Tools Only”
> installation. With this you can avoid having to enter the service
> account information that will not be needed. However, the only tools you
> get are dig.exe, nslookup.exe, and a
Hello,
I have had a couple of INSIST messages in my general log. I am running
BIND 9.6-ESV-R4-P3. Can someone enlighten me as to why I would be getting
these? Out of over 125 machines, this is the only one that has logged this
message starting yesterday. This is a recursive authoritativ
Yes, it's quite possible to split named.conf into separate per-zone .conf files
and then 'include' them back into named.conf. You can even put the list of
include statements in a separate file, and then include that into named.conf.
named.conf:
options {
[...]
}
include "/path/to/etc/zo
On Feb 16, 2012, at 7:22 AM, Tom Schmitt wrote:
>> Von: Tony Finch
>
>>> Does anyone know if there is a way to prevent the creation of certain
>>> records - by name?
>>
>> update-policy {
>> deny "*" name "internal.example.com";
>> # ...
>> };
>
> Hi,
>
> I
On Fri, 17 Feb 2012, Andrea Gozzi wrote:
> All further tests haven't produced any results.
Any related log messages in your other named logging about it. (Maybe
some isc_stdio_open error for example?)
Why were the permissions of your log file rwxrwxrwx? (Why executable?
Why writable by other?)
On Thu, 2012-02-16 at 19:06 +0100, Raven wrote:
> On Thu, 2012-02-16 at 09:55 -0600, Jeremy C. Reed wrote:
> > On Fri, 17 Feb 2012, Mark Andrews wrote:
> >
> > > > Do:
> > > >
> > > > rndc querylog
> > >
> > > or "querylog yes;"
> >
> > But the previous email showed rndc status had:
> >
> > qu
Hi,
In a recent discussion on another list, it was discussed the pros and
cons of splitting the main conf file to a per domain.
In binds case it would be to /etc/named.d/*.conf
So each zone would have a file in that directory containing only the
relevant info
eg:
zone "example.com" {
ty
20 matches
Mail list logo