Hi,
The same here.
Thibaut please read below.
On Thu, 17 Sep 2015 15:23:19 +0100 Roy Marples <r...@marples.name> wrote:
> Hi
>
> > When a zone is declared on multiple interfaces (not necessarely same
> > content, but the same name), the configuration generated doesn't work,
> > two entries are provided and this log indicates the failure at bind restart:
> > config: error: /var/lib/bind/resolvconf-zones.conf:23: zone
> > 'example.org': already exists previous definition:
> > /var/lib/bind/resolvconf-zones.conf:16
> >
> > I think it's the same problem for other resolvers.
> >
> > Maybe use the first declaration, in interfaces order and drop others ?
> > It's not perfect, but technically, the problem have no solution (if
> > zones are the same, it works perfectly, else, some zone are not reachable).
> >
> > This problem also affects the version /3.5.2-1/.
>
I cannot replicate this.
Attached is output from a system with two interfaces each of which has
DNS servers from DHCP, IPv6RA and DHCPv6.
As you can see, the final result is generated perfectly.
uberlaptop2$ resolvconf -l
# resolv.conf from wm0.dhcp
# Generated by dhcpcd from wm0.dhcp
domain marples.name
search marples.name
nameserver 10.73.2.1
# resolv.conf from wm0.dhcp6
# Generated by dhcpcd from wm0.dhcp6
search marples.name
nameserver 2a01:348:31:2::1
# resolv.conf from wm0.ra
# Generated by dhcpcd from wm0.ra
search marples.name
nameserver 2a01:348:31:2::1
# resolv.conf from iwn0.dhcp6
# Generated by dhcpcd from iwn0.dhcp6
search marples.name
nameserver 2a01:348:31:2::1
# resolv.conf from iwn0.ra
# Generated by dhcpcd from iwn0.ra
search marples.name
nameserver 2a01:348:31:2::1
uberlaptop2$ resolvconf -v
DOMAIN='marples.name'
SEARCH='marples.name'
NAMESERVERS='10.73.2.1 2a01:348:31:2::1'
LOCALNAMESERVERS='127.0.0.1'
DOMAINS='marples.name:10.73.2.1,2a01:348:31:2::1'
uberlaptop2$ cat /etc/resolvconf.conf
name_servers=127.0.0.1
unbound_conf=/usr/pkg/etc/unbound/resolvconf.conf
named_options=/tmp/named-resolvconf-options.conf
named_zones=/tmp/named-resolvconf-zones.conf
uberlaptop2$ cat /tmp/named*
# Generated by resolvconf
forward first;
forwarders {
10.73.2.1;
2a01:348:31:2::1;
};
# Generated by resolvconf
zone "marples.name" {
type forward;
forward first;
forwarders {
10.73.2.1;
2a01:348:31:2::1;
};
};
uberlaptop2$
Can you post similar output from your system please?
Mail me directly if you don't want it to appear on this public tracker.
Roy
Forwared by
--
Herbert Parentes Fortes Neto (hpfn)
