| From: | "Simon Ferrett" <sferrett@slacker.com> |
| Date: | Fri, 30 Jun 2017 23:52:39 +0000 |
| Subject: | 9.11.1-P2, 9.10.5-P2 - "key" option for also-notify/masters broken when using masters name |
| To: | bind-bugs@isc.org |
Bug Report from www.isc.org:
Name: Simon Ferrett
Email: sferrett@slacker.com
Software Version: 9.11.1-P2, 9.10.5-P2
OS: linux (centOS 6)
Subject:"key" option for also-notify/masters broken when using masters name
Bug Detail
===========
From the configuration reference:
also-notify [ port ip_port] [ dscp ip_dscp] {
( masters | ip_addr [ port ip_port ] ) [ key key_name ] ;
...
} ;
In my configuration the following works:
view test {
allow-recursion { any; };
zone "myzone.example" {
type master;
also-notify { 1.1.1.1 key trusted-key; };
file "trusted/db.myzone.example";
};
};
But the following fails (ie: if I use the name of a masters config rather than an IP address in the also-notify section):
masters mlist { 1.1.1.1; };
view test {
allow-recursion { any; };
zone "myzone.example" {
type master;
also-notify { mlist key trusted-key; };
file "trusted/db.myzone.example";
};
};
30-Jun-2017 16:43:59.070 /home/dns-master/data/conf/qs.conf:12: unexpected token 'trusted-key'
The failing config works with version 9.10.3-P2 however... so when I upgraded my configs that were using masters by name and tsig keys (in "also-notify" and "masters" zone options) began failing with "unexpected token"
Thanks-
Simon.
---
This email was received through isc.org Bug Submission Form