firmware up2date no more working named in cause

Question

Hello all, 
 I've read a lot of other testimony about problems updating. I have the same problem on my SG210. 
 I have been able to manually update firmware to the latest 9.702-1 but still stuck at patterns 166228. 
 
 I did all manipulation advised on the discussions but it still is failing to propose new patterns. I found authentication problem but I was able to identify fatal error with BIND (named) daemon. 
 Did somebody know how to repair BIND ? 
 
 2020:03:05-00:30:40 intranet named[26016]: running as: named
2020:03:05-00:30:40 intranet named[26016]: ----------------------------------------------------
2020:03:05-00:30:40 intranet named[26016]: BIND 9 is maintained by Internet Systems Consortium,
2020:03:05-00:30:40 intranet named[26016]: Inc. (ISC), a non-profit 501(c)(3) public-benefit 
2020:03:05-00:30:40 intranet named[26016]: corporation. Support and training for BIND 9 are 
2020:03:05-00:30:40 intranet named[26016]: available at https://www.isc.org/support 
2020:03:05-00:30:40 intranet named[26016]: ----------------------------------------------------
2020:03:05-00:30:40 intranet named[26016]: adjusted limit on open files from 4096 to 1048576
2020:03:05-00:30:40 intranet named[26016]: found 1 CPU, using 1 worker thread
2020:03:05-00:30:40 intranet named[26016]: using 1 UDP listener per interface
2020:03:05-00:30:40 intranet named[26016]: using up to 4096 sockets
2020:03:05-00:30:40 intranet named[26016]: loading configuration from '//etc/named.conf'
2020:03:05-00:30:40 intranet named[26016]: //etc/named.conf:146: zone 'copieur_8035_esc_c': already exists previous definition: //etc/named.conf:125
2020:03:05-00:30:40 intranet named[26016]: //etc/named.conf:555: zone 'copieur_8035_esc_c': already exists previous definition: //etc/named.conf:534
2020:03:05-00:30:40 intranet named[26016]: loading configuration: failure
2020:03:05-00:30:40 intranet named[26016]: exiting (due to fatal error) 
 Some errors. 
 
 >>> Modules::Audld::Authentication::_authenticate::158() 
 Authentication request: eu2.utmu2d.sophos.com:443/u2dauth.pl 
 >>> Modules::Audld::Authentication::_request::211() 
 Could not connect to Authentication Server eu2.utmu2d.sophos.com (code=500 500 Can't connect to eu2.utmu2d.sophos.com:443). 
 >>> Modules::Audld::Authentication::_handle_failure::235() 
 All 5 Authentication Servers failed 
 Authentication failed, no valid answer from Authentication Servers 
 
 My version. 
 Current software version...: 9.702001 
 Hardware type..............: 210r2 
 Serial number..............: xxxxxx 
 Installation image.........: 9.311-3.1 
 Installation type..........: msi 
 Installed pattern version..: 166228 
 Downloaded pattern version.: 166228 
 Up2Dates applied...........: 49 (see below) 
 sys-9.310-9.311-11.3.1.tgz (Dec 28 2016) 
 sys-9.311-9.312-3.8.1.tgz (Dec 28 2016) 
 sys-9.312-9.313-8.3.1.tgz (Dec 28 2016) 
 sys-9.313-9.314-3.13.1.tgz (Dec 28 2016) 
 sys-9.314-9.315-13.2.1.tgz (Dec 28 2016) 
 sys-9.315-9.316-2.4.1.tgz (Dec 28 2016) 
 sys-9.316-9.317-4.5.1.tgz (Dec 28 2016) 
 sys-9.317-9.318-5.5.2.tgz (Dec 28 2016) 
 sys-9.318-9.319-5.5.1.tgz (Dec 28 2016) 
 sys-9.319-9.320-5.2.2.tgz (Dec 28 2016) 
 sys-9.320-9.321-2.2.1.tgz (Dec 28 2016) 
 sys-9.321-9.350-2.12.1.tgz (Dec 28 2016) 
 sys-9.350-9.351-12.3.2.tgz (Dec 28 2016) 
 sys-9.351-9.352-3.6.2.tgz (Dec 28 2016) 
 sys-9.352-9.353-6.4.1.tgz (Dec 28 2016) 
 sys-9.353-9.354-4.4.1.tgz (Dec 28 2016) 
 sys-9.354-9.355-4.1.1.tgz (Dec 28 2016) 
 sys-9.355-9.356-1.3.1.tgz (Dec 28 2016) 
 sys-9.356-9.357-3.1.4.tgz (Dec 28 2016) 
 sys-9.357-9.358-1.3.2.tgz (Dec 28 2016) 
 sys-9.358-9.404-3.5.1.tgz (Dec 28 2016) 
 sys-9.404-9.405-5.5.1.tgz (Dec 28 2016) 
 sys-9.405-9.406-5.3.1.tgz (Dec 28 2016) 
 sys-9.406-9.407-3.3.1.tgz (Dec 28 2016) 
 sys-9.407-9.408-3.4.1.tgz (Dec 28 2016) 
 sys-9.408-9.409-4.9.1.tgz (Dec 28 2016) 
 sys-9.409-9.411-9.3.2.tgz (Feb 9 2017) 
 sys-9.411-9.412-3.2.2.tgz (Apr 20 2017) 
 sys-9.412-9.413-2.4.3.tgz (May 3 2017) 
 sys-9.413-9.414-4.2.3.tgz (Jun 26 2017) 
 sys-9.414-9.501-2.5.1.tgz (Jun 28 2017) 
 sys-9.501-9.502-5.4.1.tgz (Jul 19 2017) 
 sys-9.502-9.503-4.4.2.tgz (Sep 16 2017) 
 sys-9.503-9.504-3.1.4.tgz (Nov 1 2017) 
 sys-9.504-9.505-1.4.1.tgz (Nov 1 2017) 
 sys-9.505-9.506-4.2.2.tgz (Dec 10 2017) 
 sys-9.506-9.507-2.1.4.tgz (Mar 13 2018) 
 sys-9.507-9.508-1.10.1.tgz (Mar 13 2018) 
 sys-9.508-9.509-10.3.2.tgz (May 7 2018) 
 sys-9.509-9.510-3.5.2.tgz (Aug 19 2018) 
 sys-9.510-9.600-5.5.1.tgz (Mar 26 2019) 
 sys-9.600-9.601-5.5.2.tgz (Mar 26 2019) 
 sys-9.601-9.602-5.3.1.tgz (May 16 2019) 
 sys-9.602-9.603-3.1.1.tgz (Jun 9 2019) 
 sys-9.603-9.604-1.2.1.tgz (Aug 3 2019) 
 sys-9.604-9.605-2.1.4.tgz (Aug 3 2019) 
 sys-9.605-9.700-1.5.2.tgz (Mar 3 21:18) 
 sys-9.700-9.701-5.6.1.tgz (Mar 4 01:33) 
 sys-9.701-9.702-6.1.1.tgz (Mar 4 01:40) 
 Up2Dates available.........: 0 
 Factory resets.............: 0 
 Timewarps detected.........: 1

Jaydeep · Answer

Hi Sophos User218 
 This issue happens most of the time due to the upstream proxy server. Would you please check that UTM 9 has proper access to the internet?

Sophos User218 · Answer

Yes, you were right. 
 But I did identify an internet problem as it was not able to do a nslookup. 
 The error I found was in DNS PROXY logs, BIND doesn't start due to a fatal error. 
 I finally find out that a dns name for a device was causing the dns problem. It is a real pity than an update cause such like problems that was not a question in previous version. 
 Luckily you are there and the whole community to guide me finding the problem. 
 
 Jaydeep said: 
 Hi Sophos User218 
 This issue happens most of the time due to the upstream proxy server. Would you please check that UTM 9 has proper access to the internet?