Nameserver not resolving - Help

I have been struggliing with this for the whole day.

My domain is registered and I have updated nameserver at the registrar to use ns1.domain.com and ns2.domain.com

I have created a glue record for domain.com pointing to my IP address.

Is there a reason I am getting this error message?

Sorry, we couldn’t find any name servers for ‘thecareforcesolutions.co.uk’?

I have another domain which cloudflare is managing the DNS, I just pointed the A record to my IP and it works.

Is there a reason the nameserver is not working?

Yes, you need to create the DNS zone for that domain in Hestia. Right now, your DNS server is not acting as the authoritative DNS server for that domain, either the one shown in the screenshot or the one being used as the NS.

I’m not revealing the actual domain names because you are using domain.com as an example.

Thanks, DNS zone was also created when the domain was created in hestiacp.

You must also add the A records for ns1 and ns2.

Anyway, your bind server is not serving the zone:

❯ dig @185.230.216.73 olatubosun.com

; <<>> DiG 9.20.26-1~deb13u1-Debian <<>> @185.230.216.73 olatubosun.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 38536
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: d81e635fd44ceaab010000006aa83dbd4b48c2f5d6b42aab (good)
; EDE: 18 (Prohibited)
; EDE: 20 (Not Authoritative): (recursion disabled)
;; QUESTION SECTION:
;olatubosun.com.                        IN      A

;; Query time: 27 msec
;; SERVER: 185.230.216.73#53(185.230.216.73) (UDP)
;; WHEN: Mon Sep 14 20:32:29 CEST 2026
;; MSG SIZE  rcvd: 101

Could you please show the output of these commands?

systemctl status named --no-pager -l
grep -v '\/\/' /etc/bind/named.conf
grep -v '\/\/' /etc/bind/named.conf.options

In the screenshot I only see the ns records but not the A records for ns1 and ns2.

You don’t have a zone for olatubosun.com and you have two wrong zones; ns1.olatubosun.com and ns2.olatubosun.com. You must fix it creating the correct zone and removing those two.

Oh you mean I need to to create ns1 → A → IP address and ns2 → A → IP address?

Yes.

Nope, you must create the zone for olatubosun.com

Could you please provide a link to that doc?

I’m glad you got it working :wink:

You misinterpreted that post.