Was one of the first snippets in the script, to check for the presence of whiptail and install it if not present. Suffice to say all supported OSs have this installed by default so it seems to be a wasted step (About 1 second). Should I remove it?

As of this posting Percona doesn't have an "official" repo for Bionic but there is a version at the Ubuntu PPA which I have installed and tested and is working fine in production. Will update ASAS to include this PPA version in the meantime until Percona lands a stable release.

Began testing and adding of PHP 7.2 into the PHP installer. Should have functions, variables, and a working version in less then 48 hours.

Nginx doesnt support repos for this version of Ubuntu as of yet. Hopefully they should be available by the official expected release date of October 19th. Nginx source build works fine. I have disabled access to Nginx installer for Stable and Mainline for Aardvark users until these repos are available to public.

Nginx Updated and OpenSSL updated for TLS v1.3 support.
Nginx 1.15.7 >> 1.15.9
OpenSSL openssl-1.1.0j >> openssl-1.1.1b

Compiles perfectly in latest master

With the addition of PHP 7.2 I have decided to remove support for PHP 5.6. Only PHP 7 and above are supported now and in all honesty you should have updated your scripts for PHP 7.x. The PHP 5.x versions are very old now and don't fit into the swiftly changing technologies anymore. SO UPGRADE!

Just opening this as a reminder for myself. Still awaiting official Nginx stable and mainline repos for Ubuntu 18.04, as soon as they are available will update script. Source build has been updated and is running perfectly on Bionic.

Started work on both these options.

Mail server is tough enough from the cli but to whiptail is a whole other story, I am up for the challenge but I do think some configurations just cant be done via the GUI we will see.

Bind9 DNS is a bit simpler but DNSSEC will also be a challenge. Added Named config options to menu

Yes I have been testing some of the daily builds of the soon to be Ubuntu Server 18.04 LTS (Bionic Beaver), which is slated for April 2018. Just wanting to get a jump start on the next LTS enterprise release.

Daily Builds
http://cdimage.ubuntu.com/ubuntu-server/daily-live/current/

Perl issue after a server upgrade on Bionic (Havent run on my other version test servers yet) when compiling Nginx with OpenSSL option.

rm -rf objs/install_perl
cc -c -fPIC -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter -Werror -g -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fwrapv -fno-strict-a$
        -o objs/src/http/modules/perl/ngx_http_perl_module.o \
        src/http/modules/perl/ngx_http_perl_module.c
cc -c -fPIC -pipe  -O -W -Wall -Wpointer-arith -Wno-unused-parameter -Werror -g -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -I src/core -I src/e$
        -o objs/ngx_http_perl_module_modules.o \
        objs/ngx_http_perl_module_modules.c
cc -o objs/ngx_http_perl_module.so \
objs/src/http/modules/perl/ngx_http_perl_module.o \
objs/ngx_http_perl_module_modules.o \
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,-E -fstack-protector-strong -L/usr/local/lib -L/usr/local/lib/perl5/5.26.2/x86_64-linux/CORE -lperl -lpthread -lnsl -ldl -lm -lcryp$
-shared
/usr/bin/x86_64-linux-gnu-ld: /usr/local/lib/perl5/5.26.2/x86_64-linux/CORE/libperl.a(op.o): relocation R_X86_64_PC32 against symbol `PL_compcv' can not be used when making a shared object;$
/usr/bin/x86_64-linux-gnu-ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
objs/Makefile:1889: recipe for target 'objs/ngx_http_perl_module.so' failed
make[1]: *** [objs/ngx_http_perl_module.so] Error 1
make[1]: Leaving directory '/opt/source/nginx-1.15.2'
Makefile:8: recipe for target 'build' failed
make: *** [build] Error 2

Working on it...

Added PHP 7.4 Support
Now supports 7.2, 7.3, and 7.4 - Dropped PHP 7.1 support and prior

Updated to allow generation of 4096 bit DH cert, this improves SSL key exchanges. Nginx fully supports but Dovecot versions before 2.3 do not so path is not set for 2.2 Dovecot 10-ssl.conf. Ubuntu still has 2.2 as its base package in repo. Generating a 4096 will not effect Dovecot as it uses a 2048 generated cert in its .dat file. But when we finally update to 2.3 or if you build your own 2.3 version then you can set the path to the generated 4096 bit DH. For now its working 100% with the exception of Dovecot inclusion and will be updated once Ubuntu ups its game to Dovecot 2.3

Also added option for re-generation of DH cert
Included option to install haveged to make sure efficient entropy is available for certificate generation