On 04/22/14 13:01, Murray S. Kucherawy wrote:
> opendkim relies on resolver libraries to go get the data, and one of them
> is telling opendkim that the key isn't there. There's likely nothing in
> opendkim to debug. Assuming the details in your opendkim.conf are
> current, I can't resolve it even from the command line here:
>
> % host -t txt dkim._domainkey.caerllewys.net
> Host dkim._domainkey.caerllewys.net not found: 3(NXDOMAIN)
*DOH!!!!* I don't believe I didn't see the problem before. There's
nothing wrong with the *record* or with the nameserver. It's the
underscore in the record *name*. Underscores are not valid in a domain
name by default.
OK, I can work around this....
--
Phil Stracchino
Babylon Communications
phils_at_caerllewys.net
phil_at_co.ordinate.org
Landline: 603.293.8485
Received on Tue Apr 22 2014 - 18:59:24 PST