IPv6

Sebastian Hagedorn Hagedorn at uni-koeln.de
Wed Mar 23 11:03:10 EDT 2016


--On 23. März 2016 um 15:41:25 +0100 lst_hoe02--- via Info-cyrus 
<info-cyrus at lists.andrew.cmu.edu> wrote:

>> we've been using IPv6 for a few years now, but so far we haven't
>> used it with Cyrus. Now we want to, and I have a few questions:
>>
>> Is it correct that if we use host names in the listen statement and
>> add a AAAA record to the DNS that Cyrus will automatically listen to
>> both the IPv4 and the IPv6 address?
>>
>> I have manually added listen statements with literal IPv6 addresses
>> to cyrus.conf and HUP'ed the master, but that didn't seem to work.
>> What format do I have to use? Plain addresses (e.g.
>> 2001:DB8::6f0:484c:df5:e8b1:28cd), in brackets like in a browser
>> (e.g. [2001:DB8::6f0:484c:df5:e8b1:28cd]), sendmail-style (e.g.
>> IPv6:2001:DB8::6f0:484c:df5:e8b1:28cd) or ...? Or is the problem
>> that for changes like that I have to restart the service?
>>
>> Cheers
>> Sebastian
>
> Hm, the man page say "bracket-enclosed IP address" but until now we have
> only used the port as service name "imap" e.g. listen="imap" which works
> fine for both IPv4 and IPv6 on a dual stack host. Do you have any special
> need to use the hostname/IP address and not bind to all local addresses?

Yes, I do (multi-homed system), and I have just tried it on a test system. 
Using literal IPv6 adresses without brackets works fine, even though it 
looks strange:

  imapv6        cmd="imapd" listen="2001:DB8:0:6f0:21c:42ff:fe5e:202e:imap"

I will now try a host name with bot A and AAAA records, but I assume that 
will work as well.
-- 
    .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:.
                 .:.Regionales Rechenzentrum (RRZK).:.
   .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20160323/31daaa41/attachment.sig>


More information about the Info-cyrus mailing list