• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved DNS Server Error with b.barracudacentral.org

G J Piper

Regular Pleskian
I'm getting a ton of these in my messages log:
Code:
Jul 22 09:52:57 pcs-plesk-centos7-web-vm named[12838]: connection refused resolving '236.211.222.185.b.barracudacentral.org/A/IN': 64.235.150.189#53
Jul 22 09:52:58 pcs-plesk-centos7-web-vm named[12838]: connection refused resolving '236.211.222.185.b.barracudacentral.org/A/IN': 64.235.154.72#53
Jul 22 09:53:00 pcs-plesk-centos7-web-vm named[12838]: connection refused resolving '236.211.222.185.b.barracudacentral.org/TXT/IN': 64.235.150.189#53
Jul 22 09:53:03 pcs-plesk-centos7-web-vm named[12838]: connection refused resolving '236.211.222.185.b.barracudacentral.org/TXT/IN': 64.235.154.72#53
Jul 22 09:53:10 pcs-plesk-centos7-web-vm named[12838]: connection refused resolving '236.211.222.185.b.barracudacentral.org/A/IN': 64.235.150.189#53
Jul 22 09:53:16 pcs-plesk-centos7-web-vm named[12838]: connection refused resolving '236.211.222.185.b.barracudacentral.org/TXT/IN': 64.235.150.189#53
Jul 22 09:53:18 pcs-plesk-centos7-web-vm named[12838]: connection refused resolving '236.211.222.185.b.barracudacentral.org/TXT/IN': 64.235.154.72#53
Jul 22 09:53:38 pcs-plesk-centos7-web-vm named[12838]: connection refused resolving '106.176.231.94.b.barracudacentral.org/A/IN': 64.235.150.189#53
Jul 22 09:55:08 pcs-plesk-centos7-web-vm named[12838]: connection refused resolving '86.53.183.68.b.barracudacentral.org/A/IN': 64.235.150.189#53
Jul 22 09:55:11 pcs-plesk-centos7-web-vm named[12838]: connection refused resolving '86.53.183.68.b.barracudacentral.org/A/IN': 64.235.154.72#53
Jul 22 09:55:36 pcs-plesk-centos7-web-vm named[12838]: connection refused resolving '64.212.253.147.b.barracudacentral.org/A/IN': 64.235.150.189#53
Jul 22 09:55:36 pcs-plesk-centos7-web-vm named[12838]: connection refused resolving '64.212.253.147.b.barracudacentral.org/A/IN': 64.235.154.72#53
Jul 22 09:56:47 pcs-plesk-centos7-web-vm named[12838]: connection refused resolving '134.30.102.198.b.barracudacentral.org/A/IN': 64.235.150.189#53

the RBL does seem to still be working, as I also see in my mail log that it has blocked quite a few connections as well. But again in my mail log I also see these every so often:

Code:
Jul 22 10:19:14 pcs-plesk-centos7-web-vm postfix/smtpd[31790]: warning: 46.132.138.216.b.barracudacentral.org: RBL lookup error: Host or domain name not found. Name service error for name=46.132.138.216.b.barracudacentral.org type=A: Host not found, try again

Trying to look these up directly I get these results:
Code:
nslookup 105.218.69.64.b.barracudacentral.org
;; Got SERVFAIL reply from 169.254.169.254, trying next server
;; Got SERVFAIL reply from 208.67.222.222, trying next server
Server:       169.254.169.254
Address:   169.254.169.254#53

** server can't find 105.218.69.64.b.barracudacentral.org: NXDOMAIN
Code:
nslookup barracudacentral.org
Server:       169.254.169.254
Address:   169.254.169.254#53

Non-authoritative answer:
Name:   barracudacentral.org
Address: 64.235.154.38

Any ideas why the lookups fail on some but not others?
This just started this morning from what I can tell. See my signature for system versions.
 
We're seeing this too but on non-Plesk servers, it started yesterday at around 3am for us.
It's quite likely an issue at barracudacentral.org, so you should inquire with them or simply wait until the issue is resolved.
 
FYI: The errors stopped on our mail platforms at around 8pm yesterday. Can you @G J Piper confirm that the errors are gone now on your platform too?
 
FYI: The errors stopped on our mail platforms at around 8pm yesterday. Can you @G J Piper confirm that the errors are gone now on your platform too?

Yes. Barracuda must have fixed their problem.
I wish they had a "Current Network Status" page or something so I wouldn't have wasted half the morning looking for a problem they no-doubt knew they had at that time.
 
Back
Top