Comment 7 for bug 997076

Sorry Mathieu,

this behaviour might be correct from the dnsmask point of view. It does not work from the system or users point of view.

Thunderbird and ssh do not resolv correctly (to name but two that my users regularly use)

ping does not resolve correctly either. I have not even tried to find more applications and tools that do not work but there are a lot.

Network manager starts dnsmask with --no-resolv to ignore /etc/resolv.conf

That can be changed immediately to resolve this issue. If the resolv.conf file is left in order, things would work.

I am slightly disappointed that changes (that might be useful and required) are not communicated in advance to all parties that rely on the basic foundations. DNS resolution is basic.

Just to give you an insight into the consequences:

I have a client with 20000+ PCs. They have issues every day since 12.04. If they had rolled out 12.04, they would have had 40000 calls per day on their help desk (currently 300 - 500). My client tells me, my recommending Ubuntu was incorrect (basically boils down to I'm not worth my money) and the situation proves that Ubuntu / Linux is a playground for freaks.

So thanks for ruining another chance to establish open source by giving me and others a broken solution, a broken excuse and a broken design.

</personal frustration>