I would think to move the bug to "avahi" if you're referring
specifically to the issue with .local domains, however, I wouldn't
expect this to be fixed upstream as it's more than likely the intended
behavior. However, I would file a separate bug report under base-files
suggesting more "sane" defau
In either case, the bug isn't being caused by network-manager-pptp or
network-manager itself, but instead this bug should probably be moved to
either base-files or one of the Avahi packages.
--
network-manager (pptp?) DNS doesn't work
https://bugs.launchpad.net/bugs/174909
You received this bug n
Actually, the problem is probably stemming from your network having a
domain suffix of ".local" - Avahi (and Bonjour) use .local internally,
and that's probably what's causing it to fail to resolve properly.
There's no simple solution, but I'm almost positive that this is the
intended behavior. Si
Correction: I had forgotten about the original issue with the duplicate
entries in resolv.conf. That probably IS a bug in network-manager-pptp.
--
network-manager (pptp?) DNS doesn't work
https://bugs.launchpad.net/bugs/174909
You received this bug notification because you are a member of Ubuntu
Sorry, wins isn't necessary (I added that for my corporate network in
which wins simplifies things quite a bit), and technically the mdns4 and
mdns4_minimal shouldn't be necessary, but I'm not sure how they're being
used by the system.
--
network-manager (pptp?) DNS doesn't work
https://bugs.laun
Change the hosts line to read:
hosts: files dns wins mdns4_minimal mdns4
This won't fix the duplicate entry in resolv.conf, but it will get DNS
to resolve properly through the VPN.
--
network-manager (pptp?) DNS doesn't work
https://bugs.launchpad.net/bugs/174909
You received this bug
