# DNS works after reboot but then “Can’t reach nameserver” (AWS Lightsail)

**URL:** <https://forum.hestiacp.com/t/dns-works-after-reboot-but-then-can-t-reach-nameserver-aws-lightsail/21011>\
**Category:** DNS\
**Created:** [February 20, 2026, 9:30am UTC](https://forum.hestiacp.com/t/dns-works-after-reboot-but-then-can-t-reach-nameserver-aws-lightsail/21011 "2026-02-20T09:30:32Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dave](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/dave/32/9460_2.png) [@Dave](https://forum.hestiacp.com/u/Dave)\
**Post date:** [February 20, 2026, 9:30am UTC](https://forum.hestiacp.com/t/dns-works-after-reboot-but-then-can-t-reach-nameserver-aws-lightsail/21011/1 "2026-02-20T09:30:33Z")

</div>

Hello everyone,I’m running HestiaCP on an AWS Lightsail Ubuntu server and I’m having a DNS issue.When I reboot or stop/start the instance, everything works fine at first and my domain loads correctly. But after a few minutes, the website stops working.When I check on DNS checker tools, it shows “Can’t reach nameserver.”

NS1 and NS2 were working before, and port 53/UDP is open in the AWS firewall.Has anyone experienced this before? Why would the nameserver work after reboot and then become unreachable after a few minutes?

Thanks for your help.

---

<div class="post-metadata">

**Author:** ![Raphael](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/raphael/32/5217_2.png) [@Raphael](https://forum.hestiacp.com/u/Raphael)\
**Post date:** [February 20, 2026, 10:42am UTC](https://forum.hestiacp.com/t/dns-works-after-reboot-but-then-can-t-reach-nameserver-aws-lightsail/21011/2 "2026-02-20T10:42:23Z")

</div>

Could you please share more informations about your setup? If you run own nameserver, you need at least two different servers.

If it works after reboot, have a look at the bind9/named service to verify, that all is running properly.

---

<div class="post-metadata">

**Author:** ![Dave](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/dave/32/9460_2.png) [@Dave](https://forum.hestiacp.com/u/Dave)\
**Post date:** [February 20, 2026, 3:04pm UTC](https://forum.hestiacp.com/t/dns-works-after-reboot-but-then-can-t-reach-nameserver-aws-lightsail/21011/3 "2026-02-20T15:04:15Z")

</div>

Hello,Yes, I am using two different nameservers on two different servers:

- ns1 → 18.133.4.76

- ns2 → 3.9.102.191

Both servers have bind9 (named) installed and running.When I stop and start the instance for ns1, I am able to access it again via my domain, but after a few minutes the issue returns and DNS checker shows “Can’t reach nameserver.”

I have attached a screenshot of my DNS records for reference.

 ![IMG_6159](https://forum.hestiacp.com/uploads/default/original/2X/f/fe0b0ad20446163985d89556e4d115e153d3939e.png)

---

<div class="post-metadata">

**Author:** ![Raphael](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/raphael/32/5217_2.png) [@Raphael](https://forum.hestiacp.com/u/Raphael)\
**Post date:** [February 20, 2026, 7:20pm UTC](https://forum.hestiacp.com/t/dns-works-after-reboot-but-then-can-t-reach-nameserver-aws-lightsail/21011/4 "2026-02-20T19:20:38Z")

</div>

check the bind/named logs, probaly something fails there.

---

<div class="post-metadata">

**Author:** ![Dave](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/dave/32/9460_2.png) [@Dave](https://forum.hestiacp.com/u/Dave)\
**Post date:** [February 20, 2026, 7:59pm UTC](https://forum.hestiacp.com/t/dns-works-after-reboot-but-then-can-t-reach-nameserver-aws-lightsail/21011/5 "2026-02-20T19:59:20Z")

</div>

Is it for the ns2 or ns1?

---

<div class="post-metadata">

**Author:** ![Raphael](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/raphael/32/5217_2.png) [@Raphael](https://forum.hestiacp.com/u/Raphael)\
**Post date:** [February 20, 2026, 8:13pm UTC](https://forum.hestiacp.com/t/dns-works-after-reboot-but-then-can-t-reach-nameserver-aws-lightsail/21011/6 "2026-02-20T20:13:11Z")

</div>

both, check the logs 🙂

---

<div class="post-metadata">

**Author:** ![Dave](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/dave/32/9460_2.png) [@Dave](https://forum.hestiacp.com/u/Dave)\
**Post date:** [February 21, 2026, 2:38pm UTC](https://forum.hestiacp.com/t/dns-works-after-reboot-but-then-can-t-reach-nameserver-aws-lightsail/21011/7 "2026-02-21T14:38:30Z")

</div>

Solved

The issue was due to low RAM on a 2GB server. Adding swap fixed the instability and everything is now working fine. Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://forum.hestiacp.com/uploads/default/original/1X/d9a5b68bf50ced83e880b56452e592b204761b19.png) [@system](https://forum.hestiacp.com/u/system)\
**Post date:** [March 23, 2026, 2:39pm UTC](https://forum.hestiacp.com/t/dns-works-after-reboot-but-then-can-t-reach-nameserver-aws-lightsail/21011/8 "2026-03-23T14:39:21Z")

</div>

Closed on March 23, 2026, 2:39pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
