Unable to resolve nameserver - can't connect to website

[accafella]

Hello, I am getting reports of inability to connect to my website from various trusted sources.

I immediately assumed a blacklisting in CSF so I added the ip addresses to the whitelist but no improvement.

I am a little concerned by the following line in the CSF check security page in the WHM
Check nameservers : Unable to resolve nameserver [REDACTED]

in the WHM zone manager there is an entry for my domain and then a whole load of entries for what look like nameservers, including nameservers I no longer use. Could these be conflicting and causing the connexion issues ?

Thanks

 

[cPanelAnthony]

Hello! Before I removed your hostname for security purposes, I ran the domain through a DNS checker and am not seeing DNS issues. What exact error do you see when trying to visit your website?

 

[accafella]

Hello! Before I removed your hostname for security purposes, I ran the domain through a DNS checker and am not seeing DNS issues. What exact error do you see when trying to visit your website?

Thanks Anthony, the connection times out apparently.
I have since deleted all the spurious entries in the zone editor. I will need to wait until Monday to see if this has had an effect on my colleague's connection issues but the warning in the CSF security check still remain.

Running dig on my IP address with the ns switch gives this result

dig: parse of /etc/resolv.conf failed

this is the contents of my resolve.conf

search vm
# Generated by NetworkManager
# Automatically generated by OnApp
# Automatically generated by OnApp
# Automatically generated by OnApp
# Automatically generated by OnApp
# Automatically generated by OnApp
# Automatically generated by OnApp
domain
nameserver 8.8.8.8
nameserver 8.8.4.4

It's not certain that these are causing the connexion issues but they do appear to be genuine issues that we need to resolve but for now I am at a loss.
I hope this is more to go on

 

[cPRex]

Thanks for the additional details. I performed some additional DNS tests and I don't see anything wrong with the DNS configuration or nameserver configuration at this time. If you know a certain domain that is using that nameserver, you can scan that at intoDNS: checks DNS and mail servers health and that will reveal potential issues.