swilting wrote:
my record txt is like this

; DomainKeys
_domainkey.fakessh.eu.                  IN TXT  "t=y; o=-;"
fakessh._domainkey.fakessh.eu.    IN
TXT "k=rsa;t=s;p=MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBANzPkPCFCJwwhcYtThxfSA1LVWtBUlB7Z5G1rVRByvJxldnmfsD9BkrKmU2xqGCHr41Hys3tMWYktahv+pksDZ0CAwEAAQ=="

une dkimproxy

work fine in my box centos 5.3


Le samedi 20 juin 2009 à 15:12 +0100, Terry a écrit :
Thanks for your assistance I now have what you have
_domainkey.bluelight.org.uk.                  IN TXT  "t=y; o=-;"
bluelight._domainkey.bluelight.org.uk. IN TXT "k=rsa; t=y; p=long key"

Your domain tests fine here http://domainkeys.sourceforge.net/policycheck.html but mine does not and locally its the same too. I must be missing some thing silly. The emails are being signed fine though so that side of things is ok
The selector also tests fine

dig @192.168.2.199 bluelight._domain.bluelight.org.uk TXT
; <<>> DiG 9.4.2 <<>> @192.168.2.199 bluelight._domain.bluelight.org.uk TXT
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60488
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;bluelight._domain.bluelight.org.uk. IN TXT

;; AUTHORITY SECTION:
bluelight.org.uk. 3600 IN SOA ns1.bluelight.org.uk. terry.bluelight.org.uk. 2009062012 10800 3600 604800 3600

cf# dig @192.168.2.199 _domain.bluelight.org.uk TXT

; <<>> DiG 9.4.2 <<>> @192.168.2.199 _domain.bluelight.org.uk TXT
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18576
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;_domain.bluelight.org.uk.      IN      TXT

;; AUTHORITY SECTION:
bluelight.org.uk. 3600 IN SOA ns1.bluelight.org.uk. terry.bluelight.org.uk. 2009062012 10800 3600 604800 3600



_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Reply via email to