Link to home
Start Free TrialLog in
Avatar of Ben Conner
Ben ConnerFlag for United States of America

asked on

Problem adding DKIM record to BIND server

Hi,
A client gave me a dkim txt record they want added to their zone file.  This is on a copy of BIND 9.8.  Haven't added one before so this one's a learning experience.  

The zone seems to be fine with it but I have to be missing something as I can't pull it up with mxtoolbox.

The zone file is attached: cp.nam.  What am I missing on the domainkey line?  Thanks!

--Ben
Avatar of arnold
arnold
Flag of United States of America image

What is your Mailserver's setting for the DomainKeys setup?
What is the issue, you getting an error that your DKIM fails?

Do not currently have access to compare your dkim entry to a comparable.

I do not recall the public key you put inthe DomainKeys entry is broken as you have, it should bea single encryption key.
Your mailserver dkim encoding tells the location of the public key, and the criteria you use.
From, sender, etc.
Then these identifiers are then processed using the public key and need to have the same string as your mailserver has.

p=single very long line without breaks that is the public key in non-binary encoding, I think it is PEM

The " " not sure their source.
Think they might be your issue.
Avatar of Ben Conner

ASKER

We don't run the mail server--their tech gave me the txt record to drop in.  When I run a check from mxtoolbox.com, it can't find the dkim key for this domain.  He may have given me a wrong txt file.  Will dig further and let you know.
I did check and a txt record can have as an argument a set of text strings as long as they are all < 256 characters.

Thanks!

--Ben

SOLUTION
Avatar of arnold
arnold
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks.  I just set it up on my own mail server w/ no problems, so now I also have a working example.  You're right...something's honked up with their txt record.  Will try removing the double quotes and see what happens.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
That did the trick; combining all the separate strings into 1 let the record be seen by other name servers looking for DKIM records.  Now I have other things to sort through but this one isn't one of them.

Thanks so much for your help!

--Ben