11:16 <bramford> While not specifically related to MirageOS - I'm struggling to debug this issue with the `tls` library - https://gist.github.com/bramford/93212ddff807bc131d1562197f5f2d01

11:18 <bramford> The above works when using the `ssl` library but given this code is intended to be part of a mirage unikernel, that's not an option.

11:19 <ansiwen> What is the right way to specify the DNS server if I don't use DHCP but a static IP configuration? I don't find an example for this, surprisingly...

11:25 <bramford> ansiwen: The `http-fetch` example shows the use of a custom resolver - https://github.com/mirage/mirage-skeleton/tree/master/device-usage/http-fetch

11:27 <ansiwen> bramford: thanks for your response! it does instantiate a resolver, yes, but I don't see how I can specify a DNS server there?

11:29 <bramford> ansiwen: You can give the `resolver_dns` function optional arguments to describe the nameserver

11:29 <ansiwen> I see in the source code, that "resolver_dns" takes an "ns" and "ns_port" parameter, but I would like to see an example how to use that. I would normally go ahead and create a new unikernel command line parameter for the dns server and feed that one into the ns: pparameter of resolver_dns... but I would like to hear from someone, that it's correct thing to do.

11:31 <bramford> ansiwen: If you want to make it configurable at runtime, I don't know of any other way to do it.

11:33 <ansiwen> bramford: yes, it must be configurable at boot time

11:33 <ansiwen> bramford: thanks for your confirmation