TXT / SPF records for DNS

nobaloney

nobaloney

NoBaloney Internet Svcs - In Memoriam †
Joined
Jun 16, 2003
Messages
25,333
Location
California
First let me start by writing that I don't like SPF, and that I think the whole SPF concept is flawed.

That said, I, and many of my clients, are going to be forced to create and support SPF records or email from our domains is going to be blocked.

So here's a feature request :) :

Please, DA, consider either creating a method for us to create SPF records, or at least TXT records, so we can create SPF records ourselves.

Thanks.

Jeff
 
I can't see it in my control panel ... is this through telnet access that this can be controlled?

Ashley
 
As soon as you upgrade to 1.222 all DNS zones will be overwritten with new zones including SPF records.

Formatted this way:

domain.tld. IN TXT "v=spf1 ~all"
 
wdv said:
As soon as you upgrade to 1.222 all DNS zones will be overwritten with new zones including SPF records.

Formatted this way:

domain.tld. IN TXT "v=spf1 ~all"
Click to expand...

It should.

On my server, and perhaps on ALL servers, it doesn't.

On my server it doesn't show up at all, because I've got a custom named.db template in the custom directory.

But I looked at the template at

/usr/local/directadmin/data/templates/named.db

and it has the wrong information, based on the wrong information in my original request to DA.

I brought the mistake to their attention on July 1st, and brought my error to everyone's attention in the thread you references.

But nevertheless, currently the template says "-all", and not "~all".

It needs to be fixed. I'll bring it to DA's attention again in a moment.

Jeff
 
Hello,

The template has been changed to ~all for the last release (1.22.3).. but a write of the zone files were not issued. If you want to rewrite all zone files, run:

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

If you have -all and not ~all in the named.db template, double check that you have the most recent release of DirectAdmin.

John
 
Thanks for the clarification, John.

To this, though, I'd like to add a reminder that if you have your own custom template, you'll have to add the code to that; we did, and it didn't get added automagically.

Jeff
 
jlasman said:
Thanks for the clarification, John.

To this, though, I'd like to add a reminder that if you have your own custom template, you'll have to add the code to that; we did, and it didn't get added automagically.

Jeff
Click to expand...

That's the trade-off with custom files :)

I had the same problems with custom vhost files ;)
 
You must log in or register to reply here.
Back
Top