bad config or no config ?

hey all
i have a server at home with static public ip (router with port forwarding 80,443 and 53 for dns in case i need it) running hestiacp
i added 3 domains to hestiacp (with no dns support)
example.com , example2.com and example3.com
so i begin installing phpbb on example.com. all went okay (got some mysql errors but went fine anyway)
i had example2.com running for a month with wordpress using ip redirect from hosting that i have for A zone.
yesterday on my registrar i added custom name server “ns1/2.example.com” with my public server ip

so i changed to all 3 domains ns1 and ns2.example.com and they started working fine. some odd loading pages(slow) but it worked.
now i tried and all of them are down. if i ping the server ip it responds back with 20ms.
sometime example.com works with very slow first load… like 10 seconds for the first page to load. and the rest of the domains example2 and 3 are not working anymore.
accessing hestiacp from ip works perfectly fine.(admin pannel)
today none of the domains work.
can someone please tell me what did i do wrong and what to do ?
i just want my domains to be hosted home

It sounds like you've encountered a few issues in setting up your domains on a home server with HestiaCP, including DNS configuration and server responsiveness. Here are some steps and checks to help diagnose and potentially resolve the issues:

1. DNS Configuration Check

• DNS Records: Verify that the DNS records for ns1.example.com and ns2.example.com are correctly pointing to your public static IP. These records should be A records in your DNS settings.
• Propagation: DNS changes can take up to 48 hours to propagate fully. Use tools like dig or nslookup to check if your DNS settings have propagated. You can run dig +trace example.com to see how the DNS resolution is happening.
• DNS Server Functionality: Since you are running your own DNS, ensure that the DNS service (BIND, Unbound, etc.) is correctly configured and running on your server. Check the DNS service logs for any errors.

2. Server and Network Configuration

• Port Forwarding: Double-check that your router's port forwarding for ports 80, 443, and 53 is correctly set up. Incorrect port forwarding can lead to inaccessible services.
• Firewall Settings: Ensure that your server's firewall is allowing traffic on the necessary ports (80, 443, 53). Both inbound and outbound rules need to be configured properly.
• Server Resources: Monitor the server's resource usage (CPU, RAM, Disk I/O) when trying to access your domains. High resource usage can cause slow loading times. Tools like top, htop, or iotop can be useful.

3. HestiaCP and Web Applications

• HestiaCP Configuration: Check HestiaCP for any errors or warnings regarding the web server or database services. Make sure that PHP, MySQL, and your web server (Nginx/Apache) are properly configured.
• Error Logs: Look at the web server logs (e.g., Apache or Nginx logs) and PHP logs for any errors that might indicate what's causing the slow loading or downtime.
• Application-Specific Issues: Since you mentioned issues with PHPBB and Wordpress, check their configuration files and error logs. Sometimes, specific settings or plugins can cause performance issues.

4. Testing and Monitoring

• Ping and Traceroute: Continue using ping and traceroute to your domain to check connectivity and latency.
• Uptime Monitoring: Consider setting up a simple uptime monitor (many free tools are available online) that pings your server and alerts you when it goes down.

5. Back to Basics

• If issues persist, consider temporarily reverting your DNS changes (use your registrar's DNS as a test) to see if the issue is related to your DNS setup or something else on the server.

By methodically going through these checks, you should be able to identify the root cause of the issues. Hosting domains from a home server can be challenging due to dynamic IPs, network stability, and hardware limitations, so also consider the stability and reliability of your home internet connection.

Hope it helps!