dk dkim with dkimproxy

[fakessh at fakessh.eu]

I get a weird error

[swilting at localhost ~]$  host -t txt mail._domainkey.fakessh.eu. 
bitsy.mit.edu.
Using domain server:
Name: bitsy.mit.edu.
Address: 18.72.0.3#53
Aliases: 

Host mail._domainkey.fakessh.eu not found: 3(NXDOMAIN)
[swilting at localhost ~]$ 

[swilting at localhost ~]$  host -t txt mail._domainkey.renelacroute.fr. 
bitsy.mit.edu.
Using domain server:
Name: bitsy.mit.edu.
Address: 18.72.0.3#53
Aliases: 

mail._domainkey.renelacroute.fr descriptive 
text "v=DKIM1\;t=s\;k=rsa\;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC9HIrVMndj/1F6YXlOae/1CukcWClnD2iJ9zslFaM2vAEwNJNfJkq/0aVdTCNF/EVZi3x51FKg8wjGFWNbPW3eFaVt8ZjX0wBPFviKFeVDd2VCDwgKgk9xw0AW31kok8OX2Inikid+lPiEffoqZ2j2QOgnUJ7WnFfbKbNsm+MPLQIDAQAB"
[swilting at localhost ~]$ 
the 2 areas are located on the same machine

one telnet fakessh.eu 2525 its ok
its not NXDOMAIN

Le lundi 29 juin 2009 21:52, fakessh at fakessh.eu a écrit :
> i  dkimproxy update to the latest version which is in beta
>
> my secondary dns is not to me he plays tricks
>
> Le lundi 29 juin 2009 05:12, Byung-Hee HWANG a écrit :
> > "fakessh at fakessh.eu" <fakessh at fakessh.eu> writes:
> > > that right now
> > > [swilting at your-ab6cd29f8e ~]$  host -t txt
> > > fakessh.eu._domainkey.fakessh.eu. fakessh.eu._domainkey.fakessh.eu
> > > descriptive text "v=DKIM1\;
> > > t=s\;k=rsa\;p=MIG[...]
> >
> > OK, your check seems good. Then you check try again with external public
> > DNS (eg, bitsy.mit.edu) ;;
> >
> > $ host -t txt fakessh.eu._domainkey.fakessh.eu. bitsy.mit.edu.
> >
> > Sincerely,