Hi all,
The Zentyal Server 7.0 Beta version is now ready for testing. You can download it here:
http://download.zentyal.com/.beta/zentyal-7.0-development-amd64.iso
We are still polishing the Proxy and CA modules (we are aware that there are some minor issues). We are specially interested on receiving your feedback on the Samba module.
You can report any issues & bugs in this thread. All the feedback is much appreciated.
I have issues with DNS when I install AD. Before the initial Zentyal setup, "ping google.com" works (systemd-resolved takes care of the resolution). After installing the DNS in webadmin, same command won't work - "Temporary failure in name resolution".
Resolution of local names (in zentyal domain) seems to work ok.
$ dig google.com
; <<>> DiG 9.16.1-Ubuntu <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 25689
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: e3d826031e80fbfe0100000060003687fe9667feb69104e3 (good)
;; QUESTION SECTION:
;google.com. IN A
;; Query time: 24 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Jan 14 13:18:15 CET 2021
;; MSG SIZE rcvd: 67
Interface is configured with DHCP, which has 192.168.1.1 set as both DNS and gateway. Connection to DNS on that host works:
nmap -p 53 192.168.1.1
Starting Nmap 7.80 ( https://nmap.org ) at 2021-01-14 13:24 CET
Nmap scan report for 192.168.1.1
Host is up (0.0011s latency).
PORT STATE SERVICE
53/tcp open domain
Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
Directing dig @192.168.1.1 works as well.
Adding 192.168.1.1 to Forwarders has no effect.
● named.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2021-01-14 13:32:02 CET; 1s ago
Docs: man:named(8)
Main PID: 4155 (named)
Tasks: 26 (limit: 9459)
Memory: 65.2M
CGroup: /system.slice/named.service
└─4155 /usr/sbin/named -f -u bind -4
Jan 14 13:32:03 adc named[4155]: managed-keys-zone: DNSKEY set for zone '.' could not be verified with current keys
Jan 14 13:32:03 adc named[4155]: validating ./NS: no valid signature found
Jan 14 13:32:03 adc named[4155]: validating ./NS: no valid signature found
If any logs or more info helps, I'll be happy to provide it.