More info: - Seems to happen on apt-get / wget more than in firefox. - FreeBSD and Windows work fine on the same router.
Other links to same issue.... http://ubuntuforums.org/showthread.php?p=2049586 http://www.unixadmintalk.com/f39/debian-3-1-install-connection-timeout-4455/ http://www.ubuntux.org/problem-synaptic-update-manager-could-not-download-all-repository-indexes http://www.linuxforums.org/forum/debian-linux-help/52576-mozilla-wont-connect-konqueror-will-2.html http://archive.lug.boulder.co.us/Week-of-Mon-20051128/031105.html ** Description changed: Heaps of people all over the net are having issues with certain models of router sending back 1.0.0.0 for any DNS request. (Not only on Ubuntu) Usual answers include (that actually work) - Set DNS in the router manually - Set DNS in the computer manually (and lock/stop changing of resolv.conf) also - Disabling ipv6. (not proven to work) These solutions are not actually solutions at all, they are workarounds, I'm unable to find a fix for it that does not involve setting manual DNS in the PC or router, but without this I can't use Ubuntu for my clients !!! In my situation I have a standard build that needs to go worldwide with no editing or setting of manual DNS in the PC. (This also means that I can't access a clients ADSL modem to put the DNS settings in there). Windows machines work fine. It may be something about the router purporting to be a DNS Server when actually it's a DNS Forwarder? On some of the routers, installing later firmware fixes it. (But not always). Using Windows always fixes it! Why can't we do whatever windows does and have it "just work". Do a google search for Ubuntu 1.0.0.0 and you'll see how many times this issue is happening ! (One forum suggested it could it be an MTU too high / iptables issue?) This bug may be what people are meaning in Launchpad Bug #'s 24818 and - 23183 + 23183, but it was not explained in enough detail. ** Tags added: 10.0.0.0 d-link dlink dns ** Description changed: Heaps of people all over the net are having issues with certain models of router sending back 1.0.0.0 for any DNS request. (Not only on Ubuntu) + + *** + wget www.google.com ---13:43:44-- http://www.google.com/ => `index.html.2' Resolving www.google.com... 1.0.0.0 Connecting to www.google.com|1.0.0.0|:80... + **** Usual answers include (that actually work) - Set DNS in the router manually - Set DNS in the computer manually (and lock/stop changing of resolv.conf) also - Disabling ipv6. (not proven to work) These solutions are not actually solutions at all, they are workarounds, I'm unable to find a fix for it that does not involve setting manual DNS in the PC or router, but without this I can't use Ubuntu for my clients !!! In my situation I have a standard build that needs to go worldwide with no editing or setting of manual DNS in the PC. (This also means that I can't access a clients ADSL modem to put the DNS settings in there). Windows machines work fine. It may be something about the router purporting to be a DNS Server when actually it's a DNS Forwarder? On some of the routers, installing later firmware fixes it. (But not always). Using Windows always fixes it! Why can't we do whatever windows does and have it "just work". Do a google search for Ubuntu 1.0.0.0 and you'll see how many times this issue is happening ! (One forum suggested it could it be an MTU too high / iptables issue?) This bug may be what people are meaning in Launchpad Bug #'s 24818 and 23183, but it was not explained in enough detail. -- DNS Resolves everything to 1.0.0.0 intermittently on some ADSL Routers https://launchpad.net/bugs/81057 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
