Thursday, 9 June 2016

Re: ANN: DNS resolver changes in yakkety

On 9 June 2016 at 20:44, Martin Pitt <[email protected]> wrote:
> Stéphane Graber [2016-06-07 16:47 -0400]:
>> > > And so long as having a common solution can be done without regressions
>> > > and without hand wavy answers like "web browsers will just have to
>> > > switch to some new systemd DBUS API", I don't mind the change.
>> >
>> > Oh, come on.. NSS is neither a systemd API nor is it "new" in any
>> > sense of the word.. it's decades old, and with not doing it you have a
>> > lot of other breakage/restrictions. But, as Go is apparently our new
>> > hotness, we have to live with it I guess.
>>
>> I wasn't talking about NSS. I was talking about web browsers or any other
>> piece of software that needs the complete DNS reply and still should use
>> the per-domain DNS servers as setup by Network Manager.
>
> Well, I *was* talking about NSS.. If browsers do the above, that's
> still incomplete, as every other NSS module is still being
> disregarded. So my sympathies are limited, but I know I can't win a
> war with "Use our default browser Firefox then" :-)
>
> If a program wants to ignore NSS and reimplement DNS lookups, then
> indeed they either need a local DNS server or do the resolved lookup
> over D-Bus directly.

FWIW Squid also implements its own DNS lookups, it may be worth
looking into the ns lookup behaviour of other performance sensitive
services - apache, haproxy, varnish, nginx.

-Rob

--
ubuntu-devel mailing list
[email protected]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel