Enabling DKIM screwed up /etc/default!!

Submitted by Hal9000 on Mon, 11/08/2010 - 11:33

Hi there! I have Virtualmin Pro 3.82 and wanted to enable DKIM on all domains. It added DKIM records to DNS successfully, then i got this message after "Setting domain and selector in DKIM filter configuration ..": Failed to save DKIM settings : Failed to open /etc/default/dkim-filter for writing : Bad file descriptor now i wanted to look at /etc/default but... it's gone!! lrwxrwxrwx 1 root root 13 2010-11-08 18:26 /etc/default -> /etc/dkim.key what the hell happened? is there a way to recover my default folder?

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Mon, 11/08/2010 - 12:35

It seems unlikely to me that Virtualmin deleted /etc/default - instead, it is more probable that you just discovered this when trying to enable DKIM. Unless you are sure it was there before?

Submitted by Hal9000 on Mon, 11/08/2010 - 12:44

I restored a backup of the default/ folder in the meanwhile, then i retried to enable the dkim feature. it happened again! the folder got replaced by that stupid symlink... so this looks to be definetly a bug!

Submitted by JamieCameron on Mon, 11/08/2010 - 12:48

When you setup DKIM, what did you enter as the selector name?

Submitted by Hal9000 on Mon, 11/08/2010 - 13:11

i left default as i had no idea what else to put btw i did the exact same thing on a Virtualmin 3.81 GPL install some weeks ago and it went all fine. seems to be a 3.82 problem i guess...

Submitted by JamieCameron on Mon, 11/08/2010 - 13:14

Damn, you are right .. depending on where the initial DKIM config files are located, entering default could cause this :-(

Try entering something else, like 2010

Submitted by Hal9000 on Mon, 11/08/2010 - 13:19

ok, i used the name of the server and it went fine. now i have the problem that all my zones now have two domainkeys records, one named default and the other one named saturn. is there an easy way to remove all default. records from my zones?

Submitted by JamieCameron on Mon, 11/08/2010 - 13:23

Actually you could just ignore those default records if you like .. they are harmless.

Submitted by Hal9000 on Mon, 11/08/2010 - 13:24

ok i just typed default in the field and set the signing to no, the records got removed, then i re-enabled it for saturn, now the records are fine. but as we're talking about zones, i have a bonus question, now that i got you :) i need to change the refresh / ttl value of all zones (they are still very low since my server migration)... is there some command to do that?

Submitted by JamieCameron on Mon, 11/08/2010 - 18:05

You mean the TTL set in the $ttl field at the top of the zone file? You can bulk change this at Servers -> BIND DNS Server -> Update Records in Selected.