Facebook
Twitter
papahausa
Basic Pleskian
Thanks, Already updated.
-
Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
To continue sharing your ideas and feedback, please visit features.plesk.com
Input Warden Antispam & Virus Protection Extension for Plesk
danami
Silver Pleskian
@papahausa These are the only settings that you should be migrating across servers are policy settings, blacklists and whitelists.
Many settings are OS specific so you will break your server trying to migrate anything else unless each server is identical.
Many settings are OS specific so you will break your server trying to migrate anything else unless each server is identical.
Hangover2
Regular Pleskian
Is there any way to improve DCC performance — both server availability and response times — by adjusting certain settings?
Code:
# cdcc rtt
# 11/13/25 07:41:28 CET /var/lib/dcc/map
# Re-resolve names after 09:41:23 Check RTTs after 07:56:27
# 2363.78 ms threshold, 1555.11 ms average 12 total, 2 working servers
IPv6 on version=3
dcc1.dcc-servers.net,- RTT+1000 ms anon
# 2001:470:1f05:10ed::49,-
# not answering
# 2001:470:1f05:10ed::52,-
# not answering
dcc2.dcc-servers.net,- RTT+1000 ms anon
# 2001:628:404:8::63,- wuwien ID 1290
# 67% of 12 requests ok 1263.79+1000 ms RTT 100 ms queue wait
# 2a02:708:0:23::2,-
# not answering
dcc3.dcc-servers.net,- RTT+1000 ms anon
# *2604:bf00:1a0:2::2,- ID 1006
# 67% of 12 requests ok 892.55+1000 ms RTT 500 ms queue wait
# 2a0c:8540:10:1000::1204,-
# not answering
dcc4.dcc-servers.net,- RTT+1000 ms anon
# 2001:470:1f05:10ed::51,-
# not answering
# 2001:5a8:5:3b::5,-
# not answering
dcc5.dcc-servers.net,- RTT+1000 ms anon
# 2001:470:1f05:10ed::53,-
# not answering
# 2001:760:2a12:2::6,-
# not answeringMy stats are a bit better...
It looks like you're using IPv6. I wonder if that has any effect. The DCC webpage might offer some help (Distributed Checksum Clearinghouses).
Hangover2
Regular Pleskian
@Bobbbb Thanks for the suggestion — switching to IPv4 did the trick.
Code:
# 11/13/25 16:34:34 CET /var/lib/dcc/map
# Re-resolve names after 18:33:37 Check RTTs after 16:48:42
# 1256.09 ms threshold, 1232.92 ms average 12 total, 11 working servers
IPv6 off version=3
dcc1.dcc-servers.net,- RTT+1000 ms anon
# *137.208.8.63,- wuwien ID 1290
# 100% of 2 requests ok 155.11+1000 ms RTT 100 ms queue wait
# 184.23.168.46,- sonic ID 1254
# 100% of 2 requests ok 254.79+1000 ms RTT 100 ms queue wait
# 193.30.34.11,- www.nova53.net ID 1204
# 100% of 2 requests ok 156.09+1000 ms RTT 50 ms queue wait
dcc2.dcc-servers.net,- RTT+1000 ms anon
# 193.30.34.14,- www.nova53.net ID 1207
# 100% of 2 requests ok 156.10+1000 ms RTT 50 ms queue wait
# 194.119.212.6,- dcc1 ID 1182
# 100% of 2 requests ok 4000.00+1000 ms RTT 4000 ms queue wait
dcc3.dcc-servers.net,- RTT+1000 ms anon
# 72.18.213.53,- x.dcc-servers ID 104
# 100% of 2 requests ok 233.82+1000 ms RTT 100 ms queue wait
# 208.88.55.138,- ID 1006
# 100% of 2 requests ok 595.24+1000 ms RTT 500 ms queue wait
dcc4.dcc-servers.net,- RTT+1000 ms anon
# 38.124.232.227,- ID 1102
# 100% of 2 requests ok 208.51+1000 ms RTT 100 ms queue wait
# 72.18.213.49,- x.dcc-servers ID 104
# 100% of 2 requests ok 234.90+1000 ms RTT 100 ms queue wait
dcc5.dcc-servers.net,- RTT+1000 ms anon
# 157.131.0.46,- sonic ID 1255
# 100% of 2 requests ok 254.94+1000 ms RTT 100 ms queue wait
# 204.90.71.235,- MGTINTERNET ID 1170
# 100% of 2 requests ok 196.38+1000 ms RTT 100 ms queue waitdanami
Silver Pleskian
@Hangover2 Also make sure that you are running DCC as a service and not just calling the binary. We have instructions here:
docs.danami.com
DCC | Warden Anti-spam and Virus Protection Documentation
Warden Anti-spam and Virus Protection
docs.danami.com
danami
Silver Pleskian
@Hangover2 Warden will detect if DCC is setup as a service and you will see it listed on the Warden dashboard under the services section. It should run way faster then just using the DCC binary.
