how to set an ipv6 dns

Nikos Mavrogiannopoulos n.mavrogiannopoulos at gmail.com
Wed Jan 17 02:41:50 PST 2018


On Wed, Jan 17, 2018 at 9:46 AM, David Woodhouse <dwmw2 at infradead.org> wrote:
> On Wed, 2018-01-17 at 09:41 +0100, Nikos Mavrogiannopoulos wrote:
>> Hi,
>>  I got a report in ocserv that openconnect would not see an IPv6 DNS
>> address. Checking it further it seems that openconnect client would
>> only set INTERNAL_IP4_DNS with the contents of whatever the servers
>> provided (ipv4 or ipv6 address). As ocserv may send an IPv6 address,
>> that would be wrong.
>>
>> The attached patch can make openconnect set INTERNAL_IP6_DNS instead,
>> however vpnc-script doesn't seem to anything with that variable.
>>
>> Is there already some handling of IPv6 DNS addresses that I'm missing,
>> or it is not supported at this point?
>
> The INTERNAL_IP4_DNS variable is misnamed.
>
> For addresses and routes it makes sense to have separate configuration
> for IPv6 vs. Legacy IP.
>
> There is no such distinction for DNS. You don't have separate DNS
> servers for IPv6 lookups vs. legacy lookups. All the DNS servers go
> into the *same* list.

Makes sense. It seems there is some confusion about that in
vpnc-script. I'm attaching this small patch which clarifies that
there.


regards,
Nikos
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Document-the-fact-that-INTERNAL_IP4_DNS-contains-all.patch
Type: text/x-patch
Size: 1711 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20180117/635ad33f/attachment.bin>


More information about the openconnect-devel mailing list