missing space in extra_spf_value=include:mxo.xxx.eu

[Wanabo]

I've included extra_spf_value=include:mxo.xxx.eu in directadmin.conf.
It adds the value to "v=spf1 a mx ip4:xxx.xxx.xxx.xxxinclude:mxo.xxx.eu -all" but there is a space missing between the last xxx (last part of the ip address) and the include.

Seems to me a bug in DA because of the missing space.

@DirectAdmin Support , @smtalk is this indead a bug? Then please fix.
How to fix existing spf entries not 1 by 1 but in bulk?

 

[dmtinc]

Isnt a bug and is documented , you have to leave a extra space:

Version 1.45.0 | Directadmin Docs

DirectAdmin Knowledge Base

www.directadmin.com

if you want to fix your zones, you can try something like this:

sed -i 's/xxxinclude/xxx include/g' /var/named/*.db

check the content of the zones and if all its ok, reload all the zones and serial numbers :

cd /usr/local/directadmin
echo "action=rewrite&value=named" >> data/task.queue; ./dataskq d2000

 

[Wanabo]

? Thank you, was not aware this was documented.
Will try to fix with your suggestion.

 

[Wanabo]

First made a backup of the .db files and executed a tailored sed -i 's/xxxinclude/xxx include/g' /var/named/*.db to reflect my situation.
All worked ok!

After the " echo "action=rewrite&value=named" >> data/task.queue; ./dataskq d2000 " command I noticed some errors.
The remarkable thing is, the errors are all about domain pointers. So I'm not worried, but would like to know if this is normal.

TTL Override: Unable to read ./data/users/admin/domains/xxx-xxx.nl.conf : Unable to open ./data/users/admin/domains/xxx-xxx.nl.conf for reading.<br>
No such file or directory<br>

The files for domain pointers are indeed missing. The pointers are in ./data/users/admin/domains/domainname.com.pointers.
So perhaps the rewrite named script does not check if it is a pointer but assumes it is a regular domain.

 

[Wanabo]

Other odd thing is that the db files of the pointers contain old nameservers. The nameservers are not altered from pointers when moving users to an other server, where "normal" domains are.
Perhaps not necessary because the pointers are "controlled" in the virtual host of the parent domain. But merely a cosmetic inconsistency.

 

[dmtinc]

you can fix the db files of the pointers in the same way (or any word you want to replace in a file):

sed -i 's/ns1.oldnameserver.tld/ns1.newnameserver.tld/g' /var/named/*.db

 

[Wanabo]

Yeah I all ready did that. Thanks for helping!