DNS server failure crashes Maxscale

During a primary DNS failure Maxscale does not roll over to secondary and crashes with a system timeout.

cofigured:
GATEWAY=10.x.x.10
DNS1=10.x.x.190
DNS2=10.x.x.180

When DNS1 went offline:

2020-11-11 21:09:10 notice : Server 'server-2' version: 10.3.27-MariaDB-log
2020-11-12 18:39:18 error : (13633037) [mariadbbackend] getpeername()' failed on connection to 'server-2' when forming proxy protocol header. Error 107: 'Transport endpoint is not connected'
2020-11-12 18:39:18 error : (13633037) Write to Backend DCB ::ffff:X.X.X.X in state DCB_STATE_POLLING failed: 104, Connection reset by peer
2020-11-12 18:39:26 alert : Fatal: MaxScale 2.4.13 received fatal signal 6. Commit ID: faaf7f483eeb7afd75a5ca08fa258fae0d8c1456 System name: Linux Release string: NAME="CentOS Linux"
2020-11-12 18:39:26 alert : Statement currently being classified: none/unknown
2020-11-12 18:39:26 alert :
/lib64/libc.so.6(epoll_wait+0x33): :?
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0xd0): maxutils/maxbase/src/worker.cc:795
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x53): maxutils/maxbase/src/worker.cc:559
/usr/bin/maxscale(main+0x295a): server/core/gateway.cc:2339
/lib64/libc.so.6(__libc_start_main+0xf5): ??:?
/usr/bin/maxscale(): ??:?