• Second AAAA record

    From Michiel van der Vlist@2:280/5555 to All on Tue May 10 14:29:40 2016
    Hello All,

    With the recent problems with my SixXs tunnel in mind, I have added the AAAA record for the IPv6 address via my he.net tunnel to fido.vlist.eu.

    So it now fido.vlist.eu has two AAAA records:

    2001:470:1f15:1117:215:60ff:fe52:213d

    2001:7b8:2ff:3a9::2

    I am not sure if this does what I want. I had hoped that calling systems would use both, randomly or in round robin fashion, but binkd does not show me via wich channel the call came in.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20130111
    * Origin: he.net certified sage (2:280/5555)
  • From Benny Pedersen@1:261/38.20 to Michiel van der Vlist on Tue May 10 16:36:46 2016
    Hello Michiel!

    10 May 2016 14:29, Michiel van der Vlist wrote to All:

    MvdV> With the recent problems with my SixXs tunnel in mind, I have added
    MvdV> the AAAA record for the IPv6 address via my he.net tunnel to
    MvdV> fido.vlist.eu.

    MvdV> So it now fido.vlist.eu has two AAAA records:

    MvdV> 2001:470:1f15:1117:215:60ff:fe52:213d

    MvdV> 2001:7b8:2ff:3a9::2

    MvdV> I am not sure if this does what I want. I had hoped that calling
    MvdV> systems would use both, randomly or in round robin fashion, but
    MvdV> binkd does not show me via wich channel the call came in.

    this is working if caller have good dns support in there host client, its NOT binkd but the OS that should support more then one ip

    do you use openwrt ?, and local resolving dns server ?, all clients ips use the local resolving dns ?

    if so its possible to control localy what to do with more then on ip pr hostname

    but since you are here only the server you can only wish users will use both, eq you cannot force it


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.2.0 (Linux/4.5.3-gentoo (i686))
    * Origin: openvpn on its way here (1:261/38.20)