I'm just taking my first steps with Linux and have successfully
installed Ubuntu Server on an 80 GB partition on a Mac Mini. It runs
in command-line mode. When I try to download any further files
(including a GUI) I get a lot of "Temporary failure resolving ...."
errors.
This happens with a wireless or an Ethernet connection and still
occurs ater I have re-started the router. I am due to move to a new
ISP in a couple of weeks, so do not want to start any correspondence
with my
current ISP.
I'm just taking my first steps with Linux and have successfully
installed Ubuntu Server on an 80 GB partition on a Mac Mini. It runs in command-line mode. When I try to download any further files (including
a GUI) I get a lot of "Temporary failure resolving ...." errors.
This happens with a wireless or an Ethernet connection and still occurs
ater I have re-started the router. I am due to move to a new ISP in a
couple of weeks, so do not want to start any correspondence with my
current ISP.
Liz Tuddenham wrote:
I'm just taking my first steps with Linux and have successfully
installed Ubuntu Server on an 80 GB partition on a Mac Mini. It runs in command-line mode. When I try to download any further files (including
a GUI) I get a lot of "Temporary failure resolving ...." errors.
This happens with a wireless or an Ethernet connection and still occurs ater I have re-started the router. I am due to move to a new ISP in a couple of weeks, so do not want to start any correspondence with my
current ISP.
Is the ubunto install on DHCP, or manual IP configuration?
if the former, it should get DNS setting from your router, if the latter
have you configured DNS server IPs for it?
if you haven't got a GUI installed, you'll probably need to edit /etc/resolv.conf
by hand
or possibly
/etc/netplan/somethingorother.yaml
I am just coming to> terms with the command line interface (the lasttime I used one it was
on a Teletype).OK, welcome to a vertical learning curve.
Liz Tuddenham wrote:
I am just coming to> terms with the command line interface (the lasttime I used one it was
on a Teletype).OK, welcome to a vertical learning curve.
Are you logged in as root?
What do you see if you type
cat /etc/resolv.conf
and hit return
Do you know what editor(s) you've got installed? vi? nano?
Andy Burns <usenet@andyburns.uk> wrote:try
Do you know what editor(s) you've got installed? vi? nano?
How do I find that?
18 lines of text which I cannot expoer in any way, so I would have to
type them all out by hand. The main bits appear to be:
nameserver 127.0.0.53
Small point make very sure you are installing the correct version of Ubuntu for you hardware and processor, e.g., ARM or AMD, Intel etc.
This, is the most important requirement !
Liz Tuddenham wrote:
Andy Burns <usenet@andyburns.uk> wrote:
Do you know what editor(s) you've got installed? vi? nano?
How do I find that?try
nano testfile
first
if you do get in, use ctrl-X followed by Y to exit
failing that try
vi testfile
OK, so you have both nano and vi. I like vi, but if you didn't startnano testfile
It produce two lines of boxes along the bottom of the screen with what appeared to be the keystrokes for editing commands.
if you do get in, use ctrl-X followed by Y to exit
failing that try
vi testfile
That produce a column of tildes (in blue) down the LH side of the
screen.
Liz Tuddenham wrote:
nano testfile
It produce two lines of boxes along the bottom of the screen with what appeared to be the keystrokes for editing commands.
if you do get in, use ctrl-X followed by Y to exit
failing that try
vi testfile
That produce a column of tildes (in blue) down the LH side of theOK, so you have both nano and vi. I like vi, but if you didn't start
screen.
using it several decades ago, you'll probably hate it, so I'd say stick
to using nano for now :-)
first off take a backup copy of your resolver config file
cp /etc/resolv.conf /etc/resolv.bak
Andy Burns wrote:You're not logged in as root then, you need to be ...
cp /etc/resolv.conf /etc/resolv.bak
Fell at the first hurdle:
cp: cannot create regular file 'etc/resolve.bak' : permission denied
You're not logged in as root then, you need to be ...
Andy Burns wrote:
You're not logged in as root then, you need to be ...
Or maybe ubuntu prefers sudo, try
sudo cp /etc/resolv.conf /etc/resolv.bak
then if that works
sudo nano /etc/resolv.conf
edit, save and exit as discussed before ...
Liz Tuddenham wrote:
nano testfile
It produce two lines of boxes along the bottom of the screen with what appeared to be the keystrokes for editing commands.
if you do get in, use ctrl-X followed by Y to exit
failing that try
vi testfile
That produce a column of tildes (in blue) down the LH side of theOK, so you have both nano and vi. I like vi, but if you didn't start
screen.
using it several decades ago, you'll probably hate it, so I'd say stick
to using nano for now :-)
first off take a backup copy of your resolver config file
cp /etc/resolv.conf /etc/resolv.bak
then edit the original
nano /etc/resolv.conf
it should be a fairly simple job to edit the line that says
nameserver 127.0.0.53
and make it say
nameserver 8.8.8.8
then save changes (ctrl-O)
and exit (ctrl-X)
when back at a prompt, see if you can e.g.
ping www.bbc.co.uk
if so your downloads stand half a chance ...
Andy Burns <usenet@andyburns.uk> wrote:
Liz Tuddenham wrote:
nano testfile
It produce two lines of boxes along the bottom of the screen with what appeared to be the keystrokes for editing commands.
if you do get in, use ctrl-X followed by Y to exit
failing that try
vi testfile
That produce a column of tildes (in blue) down the LH side of theOK, so you have both nano and vi. I like vi, but if you didn't start
screen.
using it several decades ago, you'll probably hate it, so I'd say stick
to using nano for now :-)
first off take a backup copy of your resolver config file
cp /etc/resolv.conf /etc/resolv.bak
then edit the original
nano /etc/resolv.conf
it should be a fairly simple job to edit the line that says
nameserver 127.0.0.53
and make it say
nameserver 8.8.8.8
then save changes (ctrl-O)
and exit (ctrl-X)
when back at a prompt, see if you can e.g.
ping www.bbc.co.uk
if so your downloads stand half a chance ...
Have done this with "sudo" prefix as suggested.
It seemed to go as described but the result was:
ping: www.bbc.co.uk: Temporary failure in name resolution
I'm just taking my first steps with Linux and have successfully
installed Ubuntu Server on an 80 GB partition on a Mac Mini.
It runs in
command-line mode.
When I try to download any further files (including
a GUI) I get a lot of "Temporary failure resolving ...." errors.
This happens with a wireless or an Ethernet connection and still occurs
ater I have re-started the router. I am due to move to a new ISP in a
couple of weeks, so do not want to start any correspondence with my
current ISP.
On 2026-10-19 11:59, Liz Tuddenham wrote:
I'm just taking my first steps with Linux and have successfully
installed Ubuntu Server on an 80 GB partition on a Mac Mini.
What version Ubuntu Server?
It runs in
command-line mode.
If that is a problem to you, I would advise simply starting again with
Ubuntu Desktop.
When I try to download any further files (including
a GUI) I get a lot of "Temporary failure resolving ...." errors.
This happens with a wireless or an Ethernet connection and still occurs ater I have re-started the router. I am due to move to a new ISP in a couple of weeks, so do not want to start any correspondence with my
current ISP.
Yes, I'm afraid this seems to be a common problem with IP4 on various versions of Ubuntu, I think IP6 may actually work, but, because here in Scotland, I use a mobile broadband connection which doesn't support IP6,
I can't actually tell.
As far as IP4 is concerned, almost certainly the fix will vary with what version you have installed. I have fixes for versions 16 and 18 which I
give below, but you've probably installed a later version, and it's
possible that neither will work.
I'm just taking my first steps with Linux and have successfully
installed Ubuntu Server on an 80 GB partition on a Mac Mini. It runs in command-line mode. When I try to download any further files (including
a GUI) I get a lot of "Temporary failure resolving ...." errors.
Have done this with "sudo" prefix as suggested.I agree, to save your own time, nuke it and start again with a GUI
It seemed to go as described but the result was:
ping:www.bbc.co.uk: Temporary failure in name resolution
Liz Tuddenham wrote:
Have done this with "sudo" prefix as suggested.
It seemed to go as described but the result was:I agree, to save your own time, nuke it and start again with a GUI
ping:www.bbc.co.uk: Temporary failure in name resolution
Liz Tuddenham wrote:
Have done this with "sudo" prefix as suggested.
It seemed to go as described but the result was:I agree, to save your own time, nuke it and start again with a GUI
ping:www.bbc.co.uk: Temporary failure in name resolution
| Sysop: | Luis Silva |
|---|---|
| Location: | Lisbon |
| Users: | 768 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 497930:42:01 |
| Calls: | 631 |
| Files: | 46,158 |
| Messages: | 15,421 |