Comment 9 for bug 1133777

Hi,

- We can still change things for Mint 16, so I'm eager to get to the bottom of this and find the best solution quickly to improve the next release.

- There are no commercial aspects here. We're configuring the "tail" of resolvconf in an efforts to bring an out of the box DNS fallback to all those who wouldn't have one.

- I still think we need to have a DNS fallback out of the box. Maybe using tail isn't the best way. I'd love to hear more feedback on that.

- I thought OpenDNS was the best alternative at the time. I respect David's comment and understand he would prefer us not to use the service by default, so we're likely to honor that. And I also understand that the lack of proper error codes is problematic for networking applications.

So with this in mind, I'm interested in learning more about this.

- Should we continue to use a fallback? I think we should... but please try to convince us if it's a bad idea.
- Should we switch to another service than OpenDNS? Yes, but then which one? (Note that we will not use Google here).
- Is using resolvconf's tail the best option? Tell us... (note that the UI, at least outside of Cinnamon, isn't maintained by us).

I look forward to your feedback. A discussion is also taking place on the forums at http://forums.linuxmint.com/viewtopic.php?uid=2&f=90&t=128529&start=20

As you can imagine this is a VERY touchy subject. People assume bad intentions, fud is spread, and it makes it harder to lead a constructive design session... not to mention Mint 16 is coming fast.

Hopefully we can talk calmly and learn from each others in an efforts to improve things in time for Mint 16.