LinkBack URL
About LinkBacksStatus: Enabled, WARNING: SPF cannot be used because this server is not a DNS server for abcdomain.com
The server is using own dns and we have setup nameservers to use for abcdomain.com.
dnsstuff report SPF 'passed'
any ideas what's wrong?
Status: Enabled, WARNING: SPF cannot be used because this server is not a DNS serv
Status: Enabled, WARNING: SPF cannot be used because this server is not a DNS server for abcdomain.com
The server is using own dns and we have setup nameservers to use for abcdomain.com.
dnsstuff report SPF 'passed'
any ideas what's wrong?
Gundamz (Gundam Zeta) : Japanese version of transformers.
Make sure you are running the latest CURRENT.
I am using 'Release'
Is 'current' safe to use?
Gundamz (Gundam Zeta) : Japanese version of transformers.
Current is a production worthy build. If you need this, you can go to CURRENT and once this functionality propagates to RELEASE, switch back to RELEASE. You can know when this functionality has propagated to RELEASE by monitoring the changelog at http://changelog.cpanel.netOriginally Posted by gundamz
Does the improvements to SPF management includes the creation of SPF records on clustered servers?
Because we have all our boxes clustered, we have no problem to create SPF records on the nameservers that coincide with the domain nameservers, but we have nameserver clustered and wanted to keep it that way.
Canthe server check if the nameserver is clustered to synchronized with the server the domain is hosted?
We searched at release notes but didn't find if this will be resolved this way.
Thanks
The only Zone modified is that on the server where the cPanel account is modified.
If so, what is the point of DNS clusteing?????
Don't get it ....
It all depends upon your particular cluster is configured.
The SPF and DomainKeys tools only modify the Zone on the local server. If your DNS Cluster is setup to replicate Zone updates to other Cluster members, then the changes will be replicated to the other Cluster members by the synchronization tools.
That is very different from the prior answer, so, if clustering is set to replicate, the change will propagate.....
Excellet....
(I imagine cpanel should have a better way to spread the word regarding changes, new features..... we are still trying to understand the new easy apache..... )
It's the same answer.
I just updated to current instead of release, same error. All domains do the same thing.
-Jay
jayntguru: In my experience it is just a matter of waiting for the changes to take effect.
I think the changes should be pushed to the DNS cluster, if possible. Mainly to stop the error being shown to the user when cPanel checks the DNS or the error message could be changed? Maybe (Could not verify SPF as working, please check back later).
My understanding of cPanel could be wrong here but don't other changes like adding a parked domain get pushed to the DNS cluster immediately? Why can't the changes to SPF do the same?
i am having the same message.
i have tried it on servers with BIND running, and servers with no BIND running (but synchronize changes to a server running BIND - using dns clustering), both showed the same results.
I believe this has to do with the NS records not matching that of what the users name servers are set to.
So for example you could have domain.com name servers on the domain registrar side set to:
ns1.mydomain.com
ns2.mydomain.com
Now you have your name server setup in WHM set to something other than ns1.mydomain.com and ns2.mydomain.com the problem comes up.
So if your ns records say
ns1.otherdomain.com
ns2.otherdomain.com
This error will show up.
i have the same NS record set at registrar and in zone files, but I still got the message.
Reply With Quote