DomainKeys and SPF

[minotauro]

Hello all,

Always when I active the DomainKeys and SPF for a domain in cPanel I receive this errors:

"WARNING: DomainKeys cannot be used because this server is not a DNS server for domain.com"

"WARNING: SPF cannot be used because this server is not a DNS server for domain.com"

The domain is created, DNS file zone is OK. What is wrong?

Thanks,
Minotauro

[darren.nolan]

I have the same reported error. DomainKeys Enabled. SPF Enabled.

But it also says because this is not your DNS server you can't have it

I setup DomainKeys and SPF prior however to this new menu feature in cPanel. (When did this appear btw.... I've never seen it before...)

[cPanelBilly]

This means that the cPanel server is not the authoritative nameserver for the domain.

[darren.nolan]

This means that the cPanel server is not the authoritative nameserver for the domain.

Umm.... Please explain...

This server is my nameserver. Unless use of custom nameservers kills this system?

[minotauro]

This means that the cPanel server is not the authoritative nameserver for the domain.

This server is the DNS server and have authoritative for this domain. And now?

[cpanelinfoseeker]

I have found that the .net and .com domains seem to be fine (I use .com nameservers) The .us and the .biz domains seem to have this error:

WARNING: DomainKeys cannot be used because this server is not a DNS server for domain.(biz or us)

They all have an identical setup in the dns zone, so I am puzzled!

Ron

[darren.nolan]

It appears that this only shows on customers who already have a SPF record in their DNS zone, OR a customer with a dedicated IP.

Despite the error, the SPF still gets updated.

[minotauro]

My domains are .com.br and others extensions (all with .br).
The cPanel support can say anything about this problem?

[cpanelnick]

My domains are .com.br and others extensions (all with .br).
The cPanel support can say anything about this problem?

What was the ticket #?

[MichaelCorleone]

I've exactly the same problem regarding SPF.

Is this a bug in cPanel or what?

Haven't tried DomainKeys though.

Also, to someone that said, I get this message for .com domains as well.

[DJ XtAzY]

Same here, as stated in my thread: http://forums.cpanel.net/showthread.php?t=75003

My server is the nameserver and is used for one main site. It uses the same domain. It simply have www,ns1,ns2,ftp,etc, as top level domain.

[MichaelCorleone]

I would like to add that it works fine for my main reseller domain.

Just not for the others/clients.

[cpanelinfoseeker]

It appears that this only shows on customers who already have a SPF record in their DNS zone, OR a customer with a dedicated IP.

Despite the error, the SPF still gets updated.

Still puzzled. I changed one of the .us domains that was on a dedicated IP to a shared IP, and it still shows bad in cPanel. An identical setup on a .com domain works fine.

Status: Enabled, WARNING: SPF cannot be used because this server is not a DNS server for domain.us

Oh well, I'll keep on trying...
Ron

[blkjck]

Still puzzled. I changed one of the .us domains that was on a dedicated IP to a shared IP, and it still shows bad in cPanel. An identical setup on a .com domain works fine.

Status: Enabled, WARNING: SPF cannot be used because this server is not a DNS server for domain.us

Oh well, I'll keep on trying...
Ron

Make sure your DNS zone for that domain is correct. Has the SOA pointing to the nameserver name of your server followed by '.' ex 'ns1.domain.us.' It should have the same name registered as a 'NS' type for that domain. ex 'domain.us. 14400 IN NS ns1.domain.us.'

[cpanelinfoseeker]

Make sure your DNS zone for that domain is correct. Has the SOA pointing to the nameserver name of your server followed by '.' ex 'ns1.domain.us.' It should have the same name registered as a 'NS' type for that domain. ex 'domain.us. 14400 IN NS ns1.domain.us.'

Ran the report on DNSstuff.com and it finds all 4 on the nameservers when I run the report. It even shows the current SPF record, so it is being delivered by the server...

I have done a side by side comparison of the records of two domains and they are identical except that I have lowered the ttl to 60 so the changes are immediate instead of 4 hours to update.

Ron