bind is not working for/resolving your domains. better check system logs and bind config. did you try restarting it?
I explained a previous post, maybe i didnât explain in the easiest terms but the answer is there, I had this very problem a few years ago and the method was put into place and has worked ever since
It wonât until the OP gets his name servers resolving to the correct ip address
on rhel derivatives it would be
systemctl status named I think on debian derivatives it is systemctl status bind
there you can see the last messages and see possible errors.
also check the logs.
you can see logs within virtualmin also.
if someone knows. Do i have first to use the registralâs dns to request an ssl certificate first and then add my custom nameserver? Is it something with https?
I also tried to troubeshoot dns and verify the NS record and i get a timeout message
I suspected this from the first post.
I know openSRS only allows glue records from the domain interface and not the overall reseller management interface. The description of the setup just sounds wrong.
OP. Can you provide a screenshot of your glue record page? I suspect your added a name server without adding the glue record.
There is no glue record field on namecheap. You do that by personal dns based on this thread
maybe you have this problem:
Problems with DNS in latest 7.40.0 version - Virtualmin - Virtualmin Community
1 Like
Thank you my friend. I was able to resolve the issue based on your suggestion. For anyone has the same problem with bind dns with the latest 7.40 version do that: thanks to @deepakdhingra
Glad it helped. Thank you.
1 Like
What was the solution?
What am I going to do with a picture. Just paste the link.
Tar
In /etc/bind/named.conf.options
Add these 2 lines:
listen-on port 53 { any; };
listen-on-v6 port 53 { any;
As shown in the screenshot above.
DNS for domain has to be enabled to see the listed lines in order to add the 2 extra lines.
@vasilisstamos thanks
The solution above is great, it says exactly what you did, but I would have also included this link, not a screenshot that is difficult to read. The link also allows for context.
Discourse has a powerful URL parser and previewer.
The solution is from @deepakdhingra. I am new to forum, i donât exactly how to do all that. I posted the screenshot because i thought that it could help sb.
@vasilisstamos I was new once and I appreciate your posting the solution in any form. 
1 Like
however in this case it has not solved the problem try
dig greekserver.cloud NS
you will get
; <<>> DiG 9.18.39-0ubuntu0.24.04.1-Ubuntu <<>> greekserver.cloud NS
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 9610
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;greekserver.cloud. IN NS
;; Query time: 4700 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Sun Oct 12 08:31:41 BST 2025
;; MSG SIZE rcvd: 46
from that you can see that the nameservers for that domain do not resolve so therefore is not accessable from the outside world
It was a test VPS. Now I know the setup to apply it to another VPS.
This was the first stage with one custom name server.
In new installation i made Right now the issue doesnât exists.