Unstable reverse DNS lookups in UI

[2opremio]

When viewing the connections of a container talking to servers with multiple A-records, the view switches the displayed server names frequently making it confusing.

I tried to record the example but I wasn't fast enough since the names displayed ended up stabilizing. Will add it later if I see it again.

[2opremio]

@inercia Are we sorting the DNS records consistently across requests when making reverse lookups? If we don't, that would explain it.

[tomwilkie]

Hmm I didn't realise it would be possible to return multiple domain names for a given IP; we should make this a list (and make the cache store multiple entries) etc

[inercia]

So what should we do? When doing a reverse resolution, should we sort all the names we get for the IP and then return the first one? Should we make it a lista and return all of them? 😕

[tomwilkie]

the later - list and return them all.

On Tue, Sep 22, 2015 at 3:38 PM, Alvaro notifications@github.com wrote:

So what should we do? When doing a reverse resolution, should we sort all
the names we get for the IP and then return the first one? Should we make
it a lista and return all of them? [image: 😕]

—
Reply to this email directly or view it on GitHub
#504 (comment).

[inercia]

Ok, I'll fix it.

[tomwilkie]

@inercia the Node.Sets PR (#522) is pretty much ready to go, so you could base a full solution to this on that.

[inercia]

@tomwilkie ok, I'll take a look