If this is a vps rather than a stand alone machine you may find that your VPS providers firewall does not have port 53 open, but many give you the ability to open the port via their vps control panel. From your screenshot firewalld has port 53 open
Just checked & yes the port is open, however you have a problem with your nameserver not resolving.
I would switch back to your registrars nameservers (namecheap) and add the correct dns records in their interface so you at least get your nameserver to resolve.
Or if you have a spare domain name use this as you nameserver but keep the dns records on your registrar’s name servers so :-
nameserver domain has A records that point to your vps IP address
e.g. ns.sparedomain.com = your vps ip address ns2.sparedomain.com = your vps ip address
then change the nameservers for greekserver.cloud to the ns.domain names you created on the spare domain.
This means your ns servers IP addresses are handled by a third party & should always resolve (unless namecheap’s dns servers fail) to the IP address of your vps and everything will work as expected, with virtualmin/webmin managing your dns
But i want use my nameservers thats why i ask all these. Also in check port tools shows port 53 closed and i don’t understand why. In firewalld shows open.
port 53 is open (as already said )
name resolution fails for your domain only. resolves other domains correctly .
so, misconfiguration for your domain.
show us the DNS page for the virtual server so we can see the records.
when you create greekserver.cloud in virtualmin go the DNS page and make sure you have ns1.greekserver.cloud with an A record to your IP and that you have NS records with ns1.greekserver.cloud for the domain.
Please take into account your nameservers don’t resolve, there is no way anybody can query them, you must get your nameservers to resolve in the first place, an not look at things that are most likely working. Again without your nameservers resolving nothing is going to work