No, not yet. If I further think about it, just increasing MAXNS does not
entirely solve the underlying problem, as glibc seems to return
"hostname not found" if the first reachable DNS server does not know it.
One example:
I connect to my employer's LAN via VPN. I am assigned a second set of
DNS servers, and usually an additional domain search suffix, e.g.
"myoffice.company.zz". So if I e.g. try to SSH into my workstation at at
work, I would need to resolve "mybox.myoffice.company.zz".
If my company's DNS server is the first in the list, it will work. But
all other resolutions will go there as well (e.h. google.com or
launchpad.net), which might adversely affect DNS performance. Also, my
company's DNS server will certainly not know "mymediaserver.athome.zz",
so I cannot reach my box at home.
If the local DNS server is first in the list (my DSL router, or my ISP's
DNS server), I won't be able to resolve any box at work.
An easy fix would be to use a local DNS server that relay requests to
the "right" DNS server based on domain suffix, but this would either
break the entire NetworkManager thing, or would need to be integrated
into it.
But as the basic problem remains, I would recommend to keep this bug on
"New".
Ciao
Martin
** Changed in: glibc (Ubuntu)
Status: Incomplete => New
--
Resolver: MAXNS should be increased
https://bugs.launchpad.net/bugs/118930
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
