Opendkim - dkim-filter - bind9 issue.

dns_rdata_fromtext: /var/lib/bind/xxxxxx.com.hosts:19: ran out of space zone xxxxxx.com/IN: loading from master file /var/lib/bind/xxxxxx.com.hosts failed: ran out of space zone xxxxxx.com/IN: not loaded due to errors. _default/xxxxxx.com/IN: ran out of space

Since virtualmin got support for opendkim things got a bit nasty with the dkim key length. Both opendkim and dkim-filter generate keys longer than 255 chars.

Is there any fix for this ?

Status: 
Closed (duplicate)

Comments

Howdy -- it actually looks like you may be running into a disk space issue there.

What does this command output:

df -h

Welll..... no.

bind has a 255 char limit on his config files.

But for your request:

Filesystem Size Used Avail Use% Mounted on
/dev/sda1 17G 836M 15G 6% /
tmpfs 506M 0 506M 0% /lib/init/rw
udev 501M 100K 501M 1% /dev
tmpfs 506M 0 506M 0% /dev/shm

The link you posted returns an Access denied

Lowering the key size in /config.cgi?virtual-server had no effect also.

Sorry, it looks like that customer had marked that ticket as private. I'll re-post Jamie's comment on the matter, and attach his fix, below. Let us know if that helps!

Jamie's comment is as follows:

I looked into this, and found the problem - in Virtualmin 3.98, the DKIM key size was increased to 2048 bits, but that is too long for the parser in some BIND version!

The fix is to split up the TXT record in the zone file. I have attached to this bug a replacement for the file /usr/share/webmin/virtual-server/dkim-lib.pl or /usr/libexec/webmin/virtual-server/dkim-lib.pl that solves the problem. Just make sure you run /etc/webmin/restart after replacing the file, and then re-enable DKIM for your domain.

This fix will also be in the next Virtualmin release.

The file at comment 6 solves the issue.

Thank you.