Comment 2 for bug 1549788

Same for me:

Feb 29 14:45:51 DOUG-64 named[1202]: connection refused resolving '19.82.133.155.in-addr.arpa/PTR/IN': 37.59.161.64#53
Feb 29 15:35:01 DOUG-64 systemd[1]: Stopping BIND Domain Name Server...
Feb 29 15:35:01 DOUG-64 named[1202]: received control channel command 'stop'
Feb 29 15:35:01 DOUG-64 named[1202]: shutting down: flushing changes
Feb 29 15:35:01 DOUG-64 named[1202]: stopping command channel on 127.0.0.1#953
Feb 29 15:35:01 DOUG-64 named[1202]: no longer listening on 127.0.0.1#53
Feb 29 15:35:01 DOUG-64 named[1202]: no longer listening on 173.180.XXX.YYY#53
Feb 29 15:35:01 DOUG-64 named[1202]: no longer listening on 192.168.111.1#53
Feb 29 15:35:01 DOUG-64 named[1202]: exiting
Feb 29 15:35:01 DOUG-64 named[1202]: ../../../lib/isc/mem.c:1229: REQUIRE(ctx->references == 1) failed
Feb 29 15:35:02 DOUG-64 systemd[1]: bind9.service: Main process exited, code=dumped, status=6/ABRT
Feb 29 15:35:02 DOUG-64 systemd[1]: Stopped BIND Domain Name Server.
Feb 29 15:35:02 DOUG-64 systemd[1]: bind9.service: Unit entered failed state.
Feb 29 15:35:02 DOUG-64 systemd[1]: bind9.service: Failed with result 'core-dump'.

As of the last few days, I also have an apparmor issue:

Feb 29 15:35:33 DOUG-64 kernel: [25130.612529] audit: type=1400 audit(1456788933.480:15): apparmor="DENIED" operation="open" profile="/usr/sbin/named" name="/proc/sys/net/ipv4/ip_local_port_range" pid=4932 comm="named" requested_mask="r" denied_mask="r" fsuid=109 ouid=0

but if I set that apparmor profile to "complain" mode, then my kernel will crash during the shutdown phase of a re-boot.

Otherwise, and as far as I know the DNS is actually working properly.