In message <52a8e44a.1070...@brandeis.edu>, John Miller writes:
> Hello folks,
>
> I'm getting ready to revamp our dynamic DNS setup here on campus, and am
> curious: what is everyone doing for update forwarding? Have you seen
> certain clients that will send updates based on NS records rather
Hello folks,
I'm getting ready to revamp our dynamic DNS setup here on campus, and am
curious: what is everyone doing for update forwarding? Have you seen
certain clients that will send updates based on NS records rather than
the SOA record?
Perhaps a better question is: has anyone been bit
In message <52a85d1b.2010...@pernau.at>, Klaus Darilion writes:
> Hi!
>
> # named -V
> BIND 9.9.3-rl.13204.02-P2
>
> I have configured slave zones with inline signing:
>
> zone "mydomain.at" {
> type slave;
> file "/etc/bind/mydomain.at";
> masters { 1.2.3.4; };
>
-Original Message-
From: Bob McDonald
Date: Wednesday, December 11, 2013 7:10 AM
To: "bind-users@lists.isc.org"
Subject: Delegation and Forwarding
>I'm a bit confused on the need for a blank forwarders statement inside of
>a zone statement in the named.conf file. Given an internal zone
In article ,
sch...@adi.com (Thomas Schulz) wrote:
> Also, also-notify does not make much sense for a slave.
A permissible configuration is one where A transfers from B, and B
transfers from C. It then makes sense for C to notify B, and B to notify
A.
--
Barry Margolin
Arlington, MA
> > For normal slave zones (unsigned) it works fine. Is this a known bug?
> > Where can I open a bug report? Any workarounds?
Bug reports can go to bind9-b...@isc.org.
> I believe that only the master can sign the zone.
> Also, also-notify does not make much sense for a slave.
With inline-signin
> Hi!
>
> # named -V
> BIND 9.9.3-rl.13204.02-P2
>
> I have configured slave zones with inline signing:
>
> zone "mydomain.at" {
> type slave;
> file "/etc/bind/mydomain.at";
> masters { 1.2.3.4; };
> key-directory "/etc/bind/keys";
> auto-dnssec main
Same problem with:
# named -V
BIND 9.9.4-P1
On 11.12.2013 13:39, Klaus Darilion wrote:
Hi!
# named -V
BIND 9.9.3-rl.13204.02-P2
I have configured slave zones with inline signing:
zone "mydomain.at" {
type slave;
file "/etc/bind/mydomain.at";
masters { 1.2.3.4; };
Hi!
# named -V
BIND 9.9.3-rl.13204.02-P2
I have configured slave zones with inline signing:
zone "mydomain.at" {
type slave;
file "/etc/bind/mydomain.at";
masters { 1.2.3.4; };
key-directory "/etc/bind/keys";
auto-dnssec maintain;
inline-signing y
The basic answer is that you use null forwarders for any domains that you
want to turn off the global forwarders.
If you have a global forwarder and then you have bob.com with a null
forwarder, bob.com and the domains below is will follow delegation.
On Dec 11, 2013 7:10 AM, "Bob McDonald" wrote:
I'm a bit confused on the need for a blank forwarders statement inside of a
zone statement in the named.conf file. Given an internal zone on a
recursive server with global forwarders, what are the situations which
would require me to code a blank forwarders statement inside of a zone
statement in
In message <20131211120707.11028b38@loki>, Tobias Wolter writes:
>
> On Wed, 11 Dec 2013 22:01:02 +1100
> Mark Andrews wrote:
>
> > create the initial zone contents and put it in master/metazone.zone.
>
> Thanks, I feared that that was a necessary step.
>
> No way around that requirement
On Wed, 11 Dec 2013 22:01:02 +1100
Mark Andrews wrote:
> create the initial zone contents and put it in master/metazone.zone.
Thanks, I feared that that was a necessary step.
No way around that requirement by built-in means, then?
-towo
signature.asc
Description: PGP signature
_
On Wed, 11 Dec 2013 10:54:30 +
Tony Finch wrote:
> Tobias Wolter wrote:
> >
> > # rndc -s localhost -c ~/rndc-localhost.conf addzone metazone. '{type
> > master; file "master/metazone.zone";};'; tail /var/log/messages -n 4
> > rndc: 'addzone' failed: file not found
> > Dec 11 10:01:15 name
In message <2013120257.60d3bb74@loki>, Tobias Wolter writes:
>
> Hello there,
>
> I'm currently experiencing a bit of a problem with the experimental
> addzone stuff. I'm on 9.9.3-P2.
>
> I've set allow-new-zones to yes in options, and toggled
> permit-empty-zones around to no avail.
>
> My pr
Tobias Wolter wrote:
>
> # rndc -s localhost -c ~/rndc-localhost.conf addzone metazone. '{type master;
> file "master/metazone.zone";};'; tail /var/log/messages -n 4
> rndc: 'addzone' failed: file not found
> Dec 11 10:01:15 named[21120]: received control channel command
> 'addzone metazone. {t
Hello there,
I'm currently experiencing a bit of a problem with the experimental
addzone stuff. I'm on 9.9.3-P2.
I've set allow-new-zones to yes in options, and toggled
permit-empty-zones around to no avail.
My problem is that a simple addzone fails by either complaining that
the file parameter
17 matches
Mail list logo
