Hmm, that gives a two-folded output: Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from appearing. Server: 192.168.2.40 Address: 192.168.2.40#53 Non-authoritative answer: mixminion.poboxes.info canonical name = poboxes.info. Name: poboxes.info Address: 66.152.97.243 (should I remove mixminion.poboxes.info from /etc/hosts?) -----Original Message----- From: owner-mixminion-dev@freehaven.net [mailto:owner-mixminion-dev@freehaven.net] On Behalf Of Nick Mathewson Sent: Sunday, March 21, 2004 11:37 PM To: mixminion-dev@freehaven.net Subject: Re: Which IP to put in mixminiond.conf? On Sun, Mar 21, 2004 at 11:29:02PM +0100, Evert Meulie wrote: [...] > I'm in the 2nd situation you mention, and have made the mentioned changed. > The server now seems to start correctly. I get 1 entry in > /var/spool/mixminion/log: > Mar 21 23:23:32.142 +0100 [WARN] Configured hostname > 'mixminion.poboxes.info' resolves to 66.152.97.243, 66.152.97.243, and > 66.152.97.243, but we're publishing the IP 213.151.153.154 > > This one doesn't make quite sense: according to > http://www.dnsstuff.com/tools/lookup.ch?name=mixminion.poboxes.info&type=A > mixminion.poboxes.info DOES point to 213.151.153.154... :-? Is it possible that the name resolves differently on your internal network than it does for the rest the world? What happens when you run "nslookup mixminion.poboxes.info" on your own computer? -- Nick Mathewson
Attachment:
smime.p7s
Description: application/pkcs7-signature