Proxmox blocking NS servers on ISPConfig Virtual Machine

[TheNoob]

Hello, I'm trying to set up ISPConfig on a Virtual Machine inside of Proxmox (host). When I try to ping the name servers, it throws this error below. The error doesn't get thrown when I ping the www or any other CName/A Record, only with NS records.

tail -f /var/log/syslog

Mar 12 23:08:25 <hostname> named[422]: client @0x7f73080448e0 <proxmox_host_ip>#43407 (ns.mywebsite.com): query (cache) 'ns.mywebsite.com/A/IN' denied
Mar 12 23:08:25 <hostname> named[422]: client @0x7f73080448e0 <proxmox_host_ip>#18551 (ns.mywebsite.com): query (cache) 'ns.mywebsite.com/AAAA/IN' denied
Mar 12 23:08:25 <hostname> named[422]: client @0x7f73080448e0 <proxmox_host_ip>#62177 (ns.mywebsite.com): query (cache) 'ns.mywebsite.com/A/IN' denied
Mar 12 23:08:25 <hostname> named[422]: client @0x7f73080448e0 <proxmox_host_ip>#7621 (ns.mywebsite.com): query (cache) 'ns.mywebsite.com/AAAA/IN' denied
Mar 12 23:08:25 <hostname> named[422]: client @0x7f73080448e0 <proxmox_host_ip>#17811 (ns.mywebsite.com): query (cache) 'ns.mywebsite.com/A/IN' denied
Mar 12 23:08:25 <hostname> named[422]: client @0x7f73080448e0 <proxmox_host_ip>#59225 (ns.mywebsite.com): query (cache) 'ns.mywebsite.com/AAAA/IN' denied
Mar 12 23:08:25 <hostname> named[422]: client @0x7f73080448e0 <proxmox_host_ip>#3167 (ns.mywebsite.com): query (cache) 'ns.mywebsite.com/AAAA/IN' denied

In /etc/resolv.conf (ISPConfig) I've tried different combinations of these (I know they're commented out, I didn't use them all at once, but mix and matched them with no luck)

#domain <MYWEBSITE.COM>
#search <MYWEBSITE.COM>
#nameserver <PROXMOX_RESOLV.CONF_IP_FROM_OVH>
#nameserver <PROXMOX_HOST_IP>
#nameserver <MY_VPS_IP>
#nameserver 8.8.8.8

Linux version is Debian 10 (For both the Proxmox host and the VM where I'm running ISPConfig)

 

[Stoiko Ivanov]

named[422]: client @0x7f73080448e0 <proxmox_host_ip>#43407 (ns.mywebsite.com): query (cache) 'ns.mywebsite.com/A/IN' denied

not too familiar with ISPConfig - but this message might inidicate that it's an issue with the bind/named/DNS-server configuration inside the guest?

I hope this helps!