Upgrade from 7.10 to 8.04 stops connection to mail server and selected internet sites
UbuntuThis forum is for the discussion of Ubuntu Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Upgrade from 7.10 to 8.04 stops connection to mail server and selected internet sites
Having just used the update manager to upgrade from 7.10 to 8.04 I have encountered a couple of problems that make no sense to me:
1. I can't get Evolution to connect to my Tiscali POP email account
either to send or receive. I have checked and re-checked the
credentials entered into the software and they are IDENTICAL to
the ones set-up on the other machines on the network. (WinXP
machines running Outlook).
Tiscali is my ISP. They have a POP server pop.tiscali.co.uk
that requires authentication to receive, and an SMTP server
smtp.tiscali.co.uk to send, that doesn't require
2. Firefox reports "Address Not Found" for some (but not all) internet
sites. This is just MAD. I can get to all sorts of sites OK
including;linuxquestions.org, facebook.com, youtube.com, and
ask.com. But tiscali.co.uk, bbc.co.uk and google.co.uk come
back with the error. I'm probably being paranoid but its
like there is some kind of filter blocking access to the sites.
I can probably live without the BBC but not being able to access
Google is a bit of a problem.
I have network and internet access (via a router/DSL connection).
This appears to be working correctly: The Linux box is visible to the router and other machines on the network, and vice versa. The update manager can connect to software sources, and so can the application manager. So I am fairly sure I am getting out onto the web.
The only thing I have noticed is that all the servers I'm having difficulty reaching appear to have .co.uk domains.
Has anyone else encountered anything like this before?
If anyone can help please be aware that I am not a technical person. I guess I know enough to be dangerous, meaning that I can follow simple instructions and configure software using a GUI. I am new to Linux as a hobby interest, I am usually baffled by any and all things "networking", and am not very confident grappling with configuration files via Terminal.
Ah now this is interesting!!!
But I'm not sure what it means...
If I ping via the domain name; i.e. "Ping www.google.co.uk"
ping reports a failure; i.e. "ping: unknown host www.google.co.uk"
However, if I ping the self-same server using its IP;
i.e. "Ping 188.8.131.52"
ping reports success; i.e.
"PING 184.108.40.206 (220.127.116.11) 56(84) bytes of data
64 bytes from 18.104.22.168: icmp_seq=1 ttl=242 time=57.6 ms
64 bytes from 22.214.171.124: icmp_seq=2 ttl=242 time=58.7 ms
64 bytes from 126.96.36.199: icmp_seq=3 ttl=242 time=57.7 ms
64 bytes from 188.8.131.52: icmp_seq=8 ttl=242 time=57.3 ms
I do not know what the line "search domain_not_set.invalid" is all about, but the other entries are:
184.108.40.206 (ns0.ja.net), and,
are "non censoring" DNS servers that I entered as "static DNS"
via my router's configuration utility. You can blame Wallace Wang
and his interesting book "Steal this computer book 4.0" for these.
Actually it was just a bit of fun months ago to see if I got
different search results if I used different DNS from my ISP's
default servers. I can remove them if you think they're causing
the issue, but surely if they were IE on the WinXP machines
would be SNAFU too?
220.127.116.11 (man-cache-0-a-1.ns.uk.tiscali.com), and,
are the ISPs default DNS
Finally, 192.168.1.1 is my router.
See anything odd here?
Although I am not in a domain, I notice from running
"System/Administration/Services" that the machine appears to
be running something called:
"Multicast DNS service discovery (avahi-daemon)"
Disabling this and re-starting the machine (not sure if this part's necessary) had no visible effect, in that networking still appears to be working fine and the ".co.uk" suffixed domains are still unreachable.
After the test I have re-enabled it just in case it was doing something important though.
This of course also solves the problem with Evolution too. The effect of changing the file is immediate (no re-boot/service re-start is required).
Now here's the problem... "resolv.conf" appears to be recreated automatically by the system during the boot process. Which means that the above is OK as a temporary workaround, but I'm really looking for a permanent fix.
IP addresses within my network are automatically allocated by my router (a Linksys WAG354g v2) which functions as the DHCP for the network.
Ubuntu's network configuration is set-up to reflect this "Automatic Configuration (DHCP)". So, I believe the software is doing what it is supposed to, it's just entering the nameservers in the wrong order while building the "resolv.conf" file.
Does anyone know if there is a way to control the ordering of the nameserver entries during this process?
I've been doing some more digging via Google and other forums and have come up with something that fixes my issue, but rather inelegantly.
The Linux box's DHCP client behaiour is apparently controlled by a file called "dhclient.conf". On this system, this is found in the directory "/etc/dhcp3". And it looks like this...
# Configuration file for /sbin/dhclient, which is included in Debian's
# dhcp3-client package.
# This is a sample configuration file for dhclient. See dhclient.conf's
# man page for more information about the syntax of this file
# and a more comprehensive list of the parameters understood by
# Normally, if the DHCP server provides reasonable information and does
# not leave anything out (like the domain name, for example), then
# few changes must be made to this file, if any.
And this gets around my ".co.uk" suffixed domain names issue!!
However, the duplicate entry for the router in the list doesn't really satisfy my desire for tidiness, and might be a cause other problems further down the line. But I don't know enough to know this.
So, where I am at is that I have groped around and stumbled upon something that "kinda" works. I am sure there is a better (correct) way of configuring the DNS search path, but I lack the skills to find it.
If there is anyone out there that does know a better way I'd be really glad to hear from you.
It seems that the "solution" I came up with on Sunday did not work at all... Well it did, but only for the duration of the IP lease issued by the DHCP whereupon access to ".co.uk" domains stopped again.
This makes NO SENSE TO ME AT ALL, but if I edit the "resolv.conf" file again, and make it look EXACTLY the same as it did before the edit (change something and put it back) access to ".co.uk" suffixed domains starts working again!
I really need help from someone who knows what they're talking about to sort this out, if anyone can spare the time.
Oh yeah, BTW, you can set up DNS on your router if it's sufficiently capable, and then remove all this stuff from happening at bootup, and set your clients to use your router as their "only" DNS lookup!
You said earlier that when you prepended domain-name-servers to be 192.168.1.1, your .co.uk problem went away. That's because your router is already set up to handle DNS, and your clients only have to look at your router for DNS?