Named "record does not start with a double-quote" errors after migrating from CL 6

Martijn6

Verified User
Joined
Jan 18, 2022
Messages
6
We've migrated our old DirectAdmin box running CloudLinux 6 to a new box running CL 8. After restoring all users and updating DNS records, we get this error when updating the serials:
Named::get_wrapped_long_line: record does not start with a double-quote.

I won't post the full log here, but here is an excerpt:

Named::get_wrapped_long_line: record does not start with a double-quote: ( "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFFSOCAQ8AMIIBCgKCAQEAxn6bVj7f1N6n7WtrgKgiIgYLq45d6wNz4INT80dfCtLQPKt5Pjparzh1h+7otP40ai/oa4wtMpaPHZDBxXeOQci"
"AuHq/LTsdthJ0+1rB/joZ8jpPjeZJUTgK8iMjq70VP14lCYz/+SgmoT73OESacD3CW9khV8BjB0klkbW8eKAYrMKXfkVxWkL3Os3P7ykAiNfBOi0ELwHPRcVUamid5QD4w/KMEDqPnXxKgiPmyyhcr"
"eOjd2O9VV612TV0gUtNMNCFa7Y7Y/aM8wnECCDukoBC7jKNlgixl9qQa9Auo6L5Dcv1D4WcohWhoYmCFYjrl4rHb6Fpqo6w24eEPuGGCwIDAQAB" )
File /var/named/xxxxxx.com.db.temp.718564.x33Fy2esT4 appears ok to named-checkzone
Named::get_wrapped_long_line: record does not start with a double-quote: ( "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8PmIIBCgKCAQEAxJY9j1vy73FIoXa1Lja/21yjk7+r7WTmltVzY7pDci4meS63D4wJOi9NunSQowsQq98EhSovFuBX77LObEIXByJ"
"DpFj7b2WzzdHsEiKagEDqF7DbbfJ9LCW6JknuXnX9ofCQcAgYgrvZJgr5APTr4xyKs9viU9vmKYrLx38PGRgqfTW3kRqKdHjqMVh8U48PtAcQ4qp+kUSSX8RJf3EaltoLIzmIOiRow9Sw53CQbEvRi"
"OhbLDHPTo8Y9v2YhsBZThE7nLz3g7oyaXb7SWiY2gzQyRzRQNlwBJq6340olhpB19+oPAEcoAImBck2LgFeFo+VylQkk3epVJFlOhchiwIDAQAB" )
File /var/named/xxxxxx.com.db.temp.718564.RUVEkJtC9n appears ok to named-checkzone

We're not sure how to fix this. I've tried running the dkim_create.sh script to create a new DKIM record for some of the domains, but this does not seem to resolve the issue as the error message persists with those domains.
 
same issue here not sure how to fix

testing it with mail-tester etc seems all good. Weird the script is giving the issue
 
Last edited:
Sorry to bump this old tread but I am running into this same error
After making an custom dns_txt.conf , tried to rewrite the DNS records for all the domains but got this error:

Named::get_wrapped_long_line: record does not start with a double-quote: ( "v=DKIM1; k=rsa;
used command:
Code:
/usr/local/directadmin/directadmin taskq --run "action=rewrite&value=named" --debug 400

EDIT:
Adding @fln @DirectAdmin Support to assist.
it looks like its an bug in DA, have it now on an different server too
 
Last edited:
I just ran into the same issue. Running latest DA with CL9, I noticed that domains were not updating on the master servers.

named::get_wrapped_long_line: record does not start with a double-quote: ( "v=DKIM1; k=rsa; p=
 
We're seeing this when importing long DKIM keys etc. Yet cannot seem to find a syntax that pleases it enough to stop the notice.

named-checkzone reports OK just before this output when we re-write zones. We can query the record just fine, so guess it's OK?

Code:
File /var/named/example.com.db.temp.2278009.dW8p8PDoLh appears ok to named-checkzone
Named::get_wrapped_long_line: record does not start with a double-quote: ( "v=DKIM1\; k=rsa\; p=REMOVED" )

It seems more likely that the DA wrapper for named has some check logic which might not be quite bang on. Either way, it seems to work!
 
According to my experience it is not an error at all. One can see these lines when running the command:

Bash:
/usr/local/directadmin/directadmin taskq --run "action=rewrite&value=named" --debug 2000

Why do you think it is an error? What results or errors do you have beside this message?
 
The message is not the error, once again. You might need to roll back and remove the custom template.

If you need to add extra records in SPF, then you'd better use the native way for it. If you are to add `include:_spf.domain.com` to all SPF records for new domain you can set:

Bash:
da config-set extra_spf_value " include:_spf.domain.com" --restart

verify the settings applied:

Bash:
da config-get extra_spf_value

it should return
Bash:
 include:_spf.domain.com

then you can of course try and rewrite DNS records. But it won't update existing DNS zones.

The existing zones should be updated separately. You will need to modify DNS zones either manually in directadmin one zone by one, or use a script for bulk updates.
 
Back
Top