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

[boatdesign]

I just tried to enable SPF and Domainkeys for a cpanel account, and am getting:

Domainkeys
Enabled, WARNING: DomainKeys cannot be used because this server is not a DNS server for mydomain.com

SPF
Enabled, WARNING: SPF cannot be used because this server is not a DNS server for mydomain.com

The only reason I can think of for this is that mydomain.com is pointed to ns1.localdomain.net ns2.localdomain.net and ns3.localdomain.net (Domain NS records are consistent with NS records reported from nameservers) whereas the primary nameservers in WHM are set to ns1.server.com ns2.server.com and ns3.server.com which may be where this section of cpanel is looking? Many years ago we consolidated servers and simply pointed ns1.localdomain.net ns2.localdomain.net and ns3.localdomain.net to three additional IPs on server.com which has worked fine until now. (named is listening on the three additional IPs as well as the IPs for ns1.server.com, etc.)

Is there a way to overcome the above error message which looks unsightly (without changing either the older domain's ns records which are in all other ways working great or whm's 3 registered default dns servers for new domains which are different?)

What exactly does this warning mean? Are they actually enabled, or are they actually not used because of the error message?

Gmail reports:
Received-SPF: neutral (google.com: main-server-ip is neither permitted nor denied by best guess record for domain of account@mydomain.com) client-ip=main-server-ip;
DomainKey-Status: good

[boatdesign]

It appears that cpanel is in fact setting up domainkeys and spf correctly, but this warning is in error.

Is there a way to get rid of this erroneous cpanel warning?

[wemail]

I too am getting this - has anybody at cPanel found out why it is happening and what to do?

As I am on shared hosting I can't reconfigure much myself!

UPDATE: There is a relevant comment in a later thread about SPF.

[cpanelnick]

It appears that cpanel is in fact setting up domainkeys and spf correctly, but this warning is in error.

Is there a way to get rid of this erroneous cpanel warning?

You'll need to open a ticket as this generally indicates a configuration problem. There were problems with this during the initial rollout however they have been resolved for quite some time.

[tribal]

I added both a SPF and Domain Key thru Cpanel.
The domain in question had one subdomain.

Four records were created, 2 for the domain and 2 for the sub domain.

When the subdomain was deleted the SPF record was deleted, but the Domain Key for the subdomain was not.

Cheers

Kevin

[wemail]

Having played around with this on my servers and on the webhosting, they all seem to set up SPF to the extent of the SPF DNS records. However, this is only beneficial for emails outgoing. Nothing seems to be done about verifying incoming email, which is the urgent need!

DomainKeys option is definitely still making comments about not being a DNS server.

[cpanelkenneth]

Having played around with this on my servers and on the webhosting, they all seem to set up SPF to the extent of the SPF DNS records. However, this is only beneficial for emails outgoing. Nothing seems to be done about verifying incoming email, which is the urgent need!

DomainKeys option is definitely still making comments about not being a DNS server.

Support for checking SPF/DomainKeys on incoming mail is in the 4.69-5 Exim RPM that is in EDGE.

[markhard]

You'll need to open a ticket as this generally indicates a configuration problem. There were problems with this during the initial rollout however they have been resolved for quite some time.

which version does fix this problem? as I'm using the latest Cpanel RELEASE R24654 and still having this problem

[manokiss]

So, is this a configuration error or those warnings means something?

Im on Release 24909 and i have enabled in one domain without warnings in one server, in another server with the same version is giving me the warnings.

Anyone from cpanel could post any instruction to know what to check in the server configuration IF is a server configuration as nick said?

Thank you!

[cPanelTodd]

Could you open a support ticket on this issue at https://tickets.cpanel.net/submit/?reqtype=tickets so we can take a deeper look at the server configuration to determine where the configuration is incorrect causing this error to occur?

[manokiss]

Thanks Todd, just submitted the ticket (#258329).

Thank you!

[webstyler]

I have similar problem

Domainkeys: Enabled, WARNING: DomainKeys cannot be used because this server is not a DNS server for server1.mydomain.com [?]

SPF: Enabled & Active (DNS Check Passed)

--


Only domainkeys have trouble, but DNS setting is ok

?

[manokiss]

I did open a ticket and they said that is only a warning and we should disregard it. But just in case open a ticket perhaps in your case is something else.

The odd thing is, is happening only in one of our servers.

Ask to our clients to disregard those warnings...that is another story.

[webstyler]

I did open a ticket and they said that is only a warning and we should disregard it. But just in case open a ticket perhaps in your case is something else.

The odd thing is, is happening only in one of our servers.

uhm.. seems not only a warning, I have check header on email sent to gmail and there is "status: unknown"
from server that have not warking there are "status: good"

tx

[wemail]

Support for checking SPF/DomainKeys on incoming mail is in the 4.69-5 Exim RPM that is in EDGE.

We are advised by our VPS provider that, in order to activate the SPF and DomainKeys via cPanel, we will have to configure our VPS as a nameserver. (Their default is that BIND is disabled and we use their separate DNS manager).

We currently have our SPF records set up in their DNS manager, but await v4.69-5 to be able to make full use of these features.

We also need to have SRS available before we activate SPF.