It's not just a bridge, something else is going on, because this works: root@cosmic-bind9-bridge:~# ip l|grep br0 root@cosmic-bind9-bridge:~# dig +short @192.168.1.1 maestro.example.internal ;; connection timed out; no servers could be reached root@cosmic-bind9-bridge:~# brctl addbr br0 root@cosmic-bind9-bridge:~# ifconfig br0 192.168.1.1 netmask 255.255.255.0 up root@cosmic-bind9-bridge:~# dig +short @192.168.1.1 maestro.example.internal 10.0.7.5
And bind9 logs show this the moment the bridge gets an IP: Oct 15 14:15:57 cosmic-bind9-bridge named[15155]: listening on IPv4 interface br0, 192.168.1.1#53 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796164 Title: After interface/IP changes, bind9 can fail to respond to queries on the new interface To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1796164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
