All installs were BIG-sized IIAB 6.7/master on 3 different kinds of Ubuntu: {18.04/Server, 18.04/Desktop, 16.04/Desktop}

The root cause is likely yesterday PR #1180 which changed "named_enabled: True" to "named_enabled: False"

1. With IIAB 6.7/master on Ubuntu 18.04 (Desktop and Server) "./iiab-network" and "./iiab-install" both repeatedly fail as follows:

TASK [network : Add location section to config file] ***************************
fatal: [127.0.0.1]: FAILED! => {"msg": "'dhcp_service2' is undefined"}
to retry, use: --limit @/opt/iiab/iiab/iiab-stages.retry

PLAY RECAP *********************************************************************
127.0.0.1 : ok=468 changed=114 unreachable=0 failed=1

root@box:~# apt -a list dnsmasq
Listing... Done
dnsmasq/bionic,bionic,now 2.79-1 all [installed]

2. On Ubuntu 16.04/Desktop, Ansible initially failed to install networking for a different reason:

TASK [network : dhcp_server may be affected - starting - user choice] **********
fatal: [127.0.0.1]: FAILED! => {"changed": false, "msg": "Unable to start service dnsmasq: Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl status dnsmasq.service" and "journalctl -xe" for details.\n"}
to retry, use: --limit @/opt/iiab/iiab/iiab-stages.retry

PLAY RECAP *********************************************************************
127.0.0.1 : ok=505 changed=121 unreachable=0 failed=1

root@box:~# apt -a list dnsmasq
Listing... Done
dnsmasq/xenial-updates,xenial-updates,xenial-security,xenial-security,now 2.75-1ubuntu0.16.04.5 all [installed]
dnsmasq/xenial,xenial 2.75-1 all

Re-running "./iiab-network" seems to have cleared things up on Ubuntu 16.04?