domains – DNS problem – the excavation shows SERVFAIL / nslookup shows that the server cannot find

I have a domain pavelskripal.cz, which is registered in the Czech domain provider and its name servers are linked to AWS Route53.

I host it from my compartment S3. This configuration recently stopped working and I can't understand what went wrong (no changes on my side).

  1. Why does AWS nslookup work and Google One does not work? (see below)
  2. What's wrong with dig + trace @ 8.8.8.8 pavelskripal.cz? (last order)

AWS Route53 settings

enter description of image here

Domain settings:

whois pavelskripal.cz

nsset: NS-PAVELSKRIPAL-CZ
nserver: ns-1302.awsdns-34.org
nserver: ns-1681.awsdns-18.co.uk
nserver: ns-415.awsdns-51.com
nserver: ns-551.awsdns-04.net
registrar: REG-WEB4U
created: 07.03.2018 23:06:05
changed: 09.03.2018 11:09:24

Nslookup succeeds (AWS)

The query to the Route53 DNS server works (the server name comes from AWS Route53):

nslookup pavelskripal.cz ns-1302.awsdns-34.org.

Server: ns-1302.awsdns-34.org.
Address: 205.251.197.22#53

Name: pavelskripal.cz
Address: 52.216.94.50

Nslookup fails (Google)

The request to Google DNS fails:

nslookup pavelskripal.cz 8.8.8.8

Server: 8.8.8.8
Address: 8.8.8.8#53

server can't find pavelskripal.cz: SERVFAIL

Dig SERVFAIL

The Dig command displays SERVFAIL:

dig pavelskripal.cz

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> pavelskripal.cz
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 31793
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;pavelskripal.cz. IN A

;; Query time: 131 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Apr 23 11:32:02 CEST 2020
;; MSG SIZE rcvd: 44

Dig + trace

And I am not able to analyze this excavation trace command. I do not see where the problem is.

dig +trace @8.8.8.8 pavelskripal.cz

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> +trace @8.8.8.8 pavelskripal.cz
; (1 server found)
;; global options: +cmd
. 85845 IN NS g.root-servers.net.
. 85845 IN NS k.root-servers.net.
. 85845 IN NS h.root-servers.net.
. 85845 IN NS c.root-servers.net.
. 85845 IN NS d.root-servers.net.
. 85845 IN NS l.root-servers.net.
. 85845 IN NS m.root-servers.net.
. 85845 IN NS i.root-servers.net.
. 85845 IN NS f.root-servers.net.
. 85845 IN NS j.root-servers.net.
. 85845 IN NS a.root-servers.net.
. 85845 IN NS b.root-servers.net.
. 85845 IN NS e.root-servers.net.
. 85845 IN RRSIG NS 8 0 518400 20200505170000 20200422160000 48903 . p0dM/vuSKrWpnMwMMqOcqI5wGiSuwu7M0QdlhfHXSKwd7xfTWP2w/l+T 5mEVmC0bflkUqXvSO5As3KgHU6H/xCIA+CpHVCqG7PqSqVz0ZXpswWNs yDCaqSa0OvpQ8xdz56m30cGcEuOTBKcenHcgG5oEPWnK6BRTpNzpsIlm ItB/8lc2JPfEEfeJank0H3VHPlzxVY43wwO8Ypv172o/7Km+6jG0h0Hf fgnChk6+waNcNvf+AbGmn3lob/5BH03ehJ5HotEd7YRdeb4dEf4ow5sP uwpiblIifXk2CrOYAFuAiU+DjYjxFBCdvR+smx+hminsxjC6klf/F2SA aSiVDg==
;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 2 ms

cz. 172800 IN NS b.ns.nic.cz.
cz. 172800 IN NS c.ns.nic.cz.
cz. 172800 IN NS d.ns.nic.cz.
cz. 172800 IN NS a.ns.nic.cz.
cz. 86400 IN DS 20237 13 2 CFF0F3ECDBC529C1F0031BA1840BFB835853B9209ED1E508FFF48451 D7B778E2
cz. 86400 IN RRSIG DS 8 1 86400 20200506050000 20200423040000 48903 . ki1m2J3TYtNnxpmbI6qBXhpyFztJMdPWLQkRL1ri9uUSXC2BAVpw8sh7 UlzEHQKjTwsVfLeK/lLAz+xEcSjQcxS3rcW+vzxVQpG/DMiQZuNmFk8Q bciGQrf2DUw4vzBdTLj/c0rv5RDCrF8nCqABIFw2qbITQJt7qVh3IICY 4IABAlzu5ftmk2Osyek63lldviBsfWcg9IwL3augsvbslToGzPL0h6fy 2iNiRAaH+aBQkxjI9+zhAGRwn+kAEH+MA2c8hlW88mKteOjk8DD1nxzi w164u/i5lfuVQWOoapJEEOaLtr4Jo4m5lq7OBHFWdYamAlYmX4p+0dwC OcZ6+A==
;; Received 626 bytes from 198.41.0.4#53(a.root-servers.net) in 16 ms

pavelskripal.cz. 3600 IN NS ns-415.awsdns-51.com.
pavelskripal.cz. 3600 IN NS ns-551.awsdns-04.net.
pavelskripal.cz. 3600 IN NS ns-1302.awsdns-34.org.
pavelskripal.cz. 3600 IN NS ns-1681.awsdns-18.co.uk.
pavelskripal.cz. 3600 IN DS 21649 5 2 F4CEAE3A81831B64E3D4E1162ACD5172F8C56443179677CDB455F742 F459A8D4
pavelskripal.cz. 3600 IN RRSIG DS 13 2 3600 20200502000508 20200418083531 44987 cz. ntrFNqObEZTSXaZvD3TVvR2GwCxJSiE+gQYBre+rXlCtibqIMAmOp6u8 oow3rQEFuUT+dXUjoHHYbZFaOTyYRQ==
;; Received 330 bytes from 193.29.206.1#53(d.ns.nic.cz) in 1 ms

pavelskripal.cz. 5 IN A 52.216.29.67
pavelskripal.cz. 172800 IN NS ns-1302.awsdns-34.org.
pavelskripal.cz. 172800 IN NS ns-1681.awsdns-18.co.uk.
pavelskripal.cz. 172800 IN NS ns-415.awsdns-51.com.
pavelskripal.cz. 172800 IN NS ns-551.awsdns-04.net.
;; Received 200 bytes from 205.251.194.39#53(ns-551.awsdns-04.net) in 22 ms

domain name system – BIND9 SERVFAIL using dig on the server UBUNTU 18

I am setting up a nextcloud + onlyoffice server on the Ubuntu 18 server and a local DNS network for my desktop.
I am not a real computer scientist, but I am tutorials and I read forums. Moreover, being in China, I do not have Google and most of my research finds irrelevant answers … I've seen many people who had a similar error to mine but no solution did not work for me. I'm sure it's an obvious but stupid mistake, but since I'm not familiar with the BIND9 syntax, I just do not see it …
here is my named.conf.local :

                zone "platform.local" IN {
master type;
file "/etc/bind/zones/db.platform.local";
//allow-transfer{211.66.139.29;};
allow-update {none; };
allow-query {any; };
};

zone "139.66.211.in-addr-arpa" IN {
master type;
file "/etc/bind/zones/db.rev.platform.local";
allow-update {none;};
};

my db.plateforme.local :

;
; BIND data file for local loopback interface
;
$ TTL 604800
@ IN SOA ns.plateform.local. root.plateforme.local. (
33; Serial
604800; Refresh
86400; try again
2419200; Expire
604800); TTL negative cover
;

; name servers - NS info
NS ns.plateform.local.

; name servers - address
ns IN A 211.66.139.29

; name servers - A records
nextcloud IN A 211.66.139.29
onlyoffice IN A 211.66.139.29

here is db.rev.plateforme.local :

;
; BIND inverted data file for local loopback interface
;
$ TTL 604800
@ IN SOA ns.plateform.local. root.plateforme.local. (
17; Serial
604800; Refresh
86400; try again
2419200; Expire
604800); TTL negative cover
;

; name servers - NS info
IN NS ns.plateform.local.
IN NS localhost.

; name servers - address
29 IN NS ns.plateform.local.

29 IN PTR nextcloud.plateform.
29 IN PTR onlyoffice.plateform.local.

Here is the result of dig nextcloud.plateform.local :

nextcloud @ nextcloud-server: / etc / bind / zones $ dig nextcloud.platform.local.
; << >> DiG 9.11.4-3ubuntu5.1-Ubuntu << >> nextcloud.plateforme.local.
;; global options: + cmd
;; Do you have the answer:
;; CAUTION: .local is reserved for multicast DNS
;; You are currently testing what happens when an mDNS query is filtered to DNS
;; - >> HEADER << - opcode: QUERY, status: SERVFAIL, id: 42787
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; PSEUDOSECTION OPT:
; EDNS: version: 0, flags:; PNU: 65494
;; SECTION QUESTION:
; nextcloud.plateforme.local. IN ONE

;; Query time: 0 msec
;; SERVER: 127.0.0.53 # 53 (127.0.0.53)
;; WHEN: Tue 12 Mar 10:25:52 HKT 2019
;; MSG SIZE rcvd: 55

and the reverse dig dig -x 211.66.139.29 it works surprisingly:

nextcloud @ nextcloud-server: / etc / bind / zones $ dig -x 211.66.139.29

; << >> DiG 9.11.4-3ubuntu5.1-Ubuntu << >> -x 211.66.139.29
;; global options: + cmd
;; Do you have the answer:
;; - >> HEADER << - opcode: QUERY, status: NOERROR, id: 63404
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; PSEUDOSECTION OPT:
; EDNS: version: 0, flags:; PNU: 65494
;; SECTION QUESTION:
; 29.139.66.211.in-addr.arpa. IN PTR

;; SECTION RESPONSE:
29.139.66.211.in-addr.arpa. 0 IN PTR nextcloud-server.
29.139.66.211.in-addr.arpa. 0 IN PTR nextcloud-server.local.

;; Time of interrogation: 120 ms
;; SERVER: 127.0.0.53 # 53 (127.0.0.53)
;; WHEN: Tue, Mar 12 10:39:53 HKT 2019
;; MSG SIZE rcvd: 121

I would be very grateful if anyone could help me … I set up this server for our team of 16 teachers because I took computer training more than ten years ago, because we we need this server and the supply on the continent. China is limited and out of reach … but I do it in addition to my teaching duties and it takes a lot of time. I would greatly appreciate the help and advice of experts.
Thank you in advance for your time!