On 21.02.2018 19:49, goldsi...@gmx.de wrote:
> On 21.02.2018 17:18, Jan Menzel wrote:
>> Hi all!
>> I'd like to share a small patch with you that allows the dns
>> subsystem
>> to remember and handle more then one IP address from response messages.
>> It basically parses out all IP address and stores them in an array. It
>> then returns a random entry.
>
> What is this used for? A good DNS server should sort the IP address list
> of a host differently for each request.
>
We have a number of devices all located behind a single public ip
address which request time from public ntp server pools. Without this
change all devices connected to the same server which just returned
Kiss-of-Death. It seems, that the router in this installation does not
qualify for a good DNS server.
> If you want your client application to load-balance although the locally
> cached DNS entry has expired, I think a better approach would be to
> actually return all available IPs to the client and let it chose one
> (i.e. implement the random algorithm in your application). That way,
> 'gethostbyname' etc. could return all entries as well.
>
Yes, this would be an option. I rejected this approach because it breaks
the api.
Jan
_______________________________________________
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
