The VestaCP DNS servers are not functioning.
The VestaCP DNS servers are not functioning.
You're facing an issue with your domain lukedyte.me pointing to VestaCP nameservers hosted on CentOS. The DNS isn't responding as expected, even though port53 is open and traffic can reach the server. It's been over 48 hours since changes took effect, and some servers still resolve it correctly while others don't. You've noticed that Cloudflare DNS works fine for you but not for other providers, which seems unusual. The A records for ns1 and ns2 are pointing to an A record, but the nameservers aren't showing up. What might help is checking your firewall settings on the CentOS VM, ensuring no rules block DNS queries, and verifying that the VestaCP server is actually accepting connections on port53. Also, double-check the nameserver configuration in your hosting control panel or CLI.
VESTACP provides a DNS solution along with a BIND named service. After setting up the details, it automatically configures itself using BIND. The unusual behavior is that your site functions properly with Cloudflare DNS but not with any other DNS provider.
Intodns mentions you're missing some records, which might cause issues. Unless you need to handle DNS manually, I strongly suggest using a DNS provider such as Cloudflare. Doing it yourself can be quite challenging.