[Bug 1186684] Re: Resolveconf generats invalid resolve.conf with commas in DNS entries

[Thomas Hood]

Ah, sorry,  I didn't understand that.  I didn't even know that Arch was
using resolvconf.

If Arch is using  resolvconf then Arch's bug tracking system is the
first place to consider filing a report. If you are convinced that the
bug comes from upstream then file a report upstream.

Resolvconf's ultimate upstream is Debian, by the way.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1186684

Title:
  Resolveconf generats invalid resolve.conf with commas in DNS entries

Status in “resolvconf” package in Ubuntu:
  Invalid

Bug description:
  I'm on Arch Linux, the latest version as of 2013 June 02.

  Resolveconf generates an invalid "/etc/resolv.conf" file with entries
  as follows:

      nameserver 123.123.123.123,
      nameserver 123.123.123.123

  As you can see the commas are unnecessary, and it breaks "pacman"
  updating, although ping works. This is because the network config is
  okay, but pacman apparently uses the "resolv.conf" data and the commas
  confuse it.

  Please stop adding commas to the "resolv.conf" file since this breaks
  important features on Arch Linux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1186684/+subscriptions