I recently got an AT&T U-verse (VDSL) connection at home (I could not
resist 24 mbps down!). When I connect to the 2Wire 3600 HGV modem/router
(DHCP) DNS is set to 192.168.1.254 in Network Manager which is the routers
own IP address and not the DNS server address(es) the modem uses which is
(read from the modem/routers config UI):
Primary DNS 188.8.131.52
Secondary DNS 184.108.40.206
This doesn't cause problems for web browsing and such, but it breaks apt
with the following error message when I for instance run sudo apt-get
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dis...ck/Release.gpg
Something wicked happened resolving 'archive.ubuntu.com:http' (-5 - No
address associated with hostname).
Looks like apt can't "see through" this setup, but I can ping the repos
(like archive.ubuntu.com) just fine.
The only way around this problem is to set DNS manually in Network Manager
(using Google, OpenDNS or AT&T's own) for the wireless connection I am
using. When I do this apt works fine and I can update without errors.
There's no way to set other DNS servers in the modem/router itself. I
suspect that has to do with this modem/router being used for VOIP and TV
services as well.
I'm no network guru so I was wondering why DNS is set to the router/modems
own IP and not to the DNS servers actually used? Is this a modem/router
problem or is it Network Manager setting it up wrong? Since I do not have
any Windows machines around I can not check if the same things happens
I'm running latest Ubuntu/Mint.