[Bug 999395] Re: 12.04 system unable to resolve us.archive.ubuntu.com with resolvconf/dnsmasq
Steve Langasek
steve.langasek at canonical.com
Tue May 15 02:45:41 UTC 2012
> Changing the nameserver in /etc/resolv.conf to point to the router makes no difference.
> Changing it to point directly to my ISP's DNS server makes name resolution work.
So it seems that this is a bug in your router's DNS server, and nothing
to do with either resolvconf or dnsmasq. You either need to edit the
network manager profile for this connection to point at your ISP's DNS
server instead of at your router, or edit your router's DHCP settings to
point at the ISP's DNS instead of at itself.
** Changed in: resolvconf (Ubuntu)
Status: New => Invalid
--
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/999395
Title:
12.04 system unable to resolve us.archive.ubuntu.com with
resolvconf/dnsmasq
Status in “resolvconf” package in Ubuntu:
Invalid
Bug description:
Install ISO: xubuntu-12.04-desktop-amd64.iso
dnsmasq-base: 2.59-4
resolvconf: 1.63ubuntu11
My first time to install 12.04, so no prior experience with
resolvconf/dnsmasq.
I used the 64-bit Xubuntu desktop CD-ROM to install to a brand-new
hard disk. The machine has a wireless interface (unused) and an
ethernet interface, which is assigned its IP address by my router via
DHCP. The generated resolv.conf (attached) points to 127.0.0.1 as the
nameserver. The nm-dns-dnsmasq.conf in turn points to the router
(192.168.3.1) as the DNS server.
The system, once installed, cannot get updates from
us.archive.ubuntu.com because of a name-resolution problem. It looks
as though any DNS query that returns a large answer (many IP addresses
for a name, e.g.), isn't handled.
cbearden at anselm:~$ host us.archive.ubuntu.com
;; Truncated, retrying in TCP mode.
Host us.archive.ubuntu.com.Belkin not found: 5(REFUSED)
cbearden at anselm:~$ host www.hal-pc.org
www.hal-pc.org has address 204.52.135.18
When the first query (UDP) is issued, the router responds with the
answer (see the attached text output of a tcpdump trace), but the
system ignores the response and queries the router via TCP, but the
connection is refused.
Changing the nameserver in /etc/resolv.conf to point to the router
makes no difference. Changing it to point directly to my ISP's DNS
server makes name resolution work.
This may be the same bug as #998712, but I'm can't tell for sure.
I'm attaching
a tar file containing
* /etc/resolv.conf
* /etc/resolvconf/*
* /run/resolvconf/
/etc/network/interfaces
/run/nm-dns-dnsmasq.conf
/var/log/syslog
and the text output of the tcpdump trace mentioned above.
I'll work around this problem manually to be able to get updates and
resolve names. Or, if I did something wrong in my setup, I'll gladly
accept instruction. :-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/999395/+subscriptions
More information about the foundations-bugs
mailing list