
P A R T I
C O N N E C T I N G T H E B O A R D
76
If you need to return to automatic settings via DHCP, you need to edit the
interfaces
file
again and delete the
address
,
netmask
and
gateway
settings. Replace
static
with
dhcp
at the end of the
iface
line, and then restart the networking service again.
Setting a manual IP address isn’t quite enough to get your Pi connected to the outside world.
Computers on modern networks have both a numerical address identifier—known as an IP
address—and a hostname or domain name. It’s this latter, friendly name that allows you
simply to type
www.raspberrypi.org
into your browser, instead of trying to remember
93.93.128.176
.
A system called a
Domain Name Service (DNS) server
is responsible for looking up the friendly
names you supply and converting them into the numbers required to access the system. It
operates much like an automated telephone directory. Before you’ll be able to access Internet-
connected systems via their domain names, you’ll need to tell the Pi which DNS servers to use.
The list of DNS servers, known as
nameservers
in Linux parlance, is stored in
/etc/resolv.
conf
. When the system gets its details through DHCP, this file is automatically filled in; but
when you set an address manually, you need to provide the addresses of the nameservers on
your network. Normally, this would be the address of your router as found in the
gateway
line from the
interfaces
file (described earlier in this chapter).
To set the nameservers, open the file with
nano
by typing the following command at the
terminal:
sudo nano /etc/resolv.conf
Add each nameserver on a separate line, prefaced with
nameserver
and a space. As an
example, the
resolv.conf
configuration for a network that uses Google’s publicly accessi-
ble nameservers to resolve domain names would appear like this:
nameserver 8.8.8.8
nameserver 8.8.4.4
You’ll notice that the nameserver addresses need to be supplied as IP addresses, rather than
domain names. If you provided domain names instead, the Pi would enter an infinite loop of
trying to find a nameserver to ask how it can find the nameservers.
Save the file by pressing CTRL + O, and then quit
nano
by pressing CTRL + X. Restart the
networking interface by typing the following:
sudo /etc/init.d/networking restart
Summary of Contents for A
Page 1: ......
Page 2: ......
Page 3: ...Raspberry Pi User Guide 2nd Edition...
Page 4: ......
Page 5: ...Raspberry Pi User Guide 2nd Edition Eben Upton and Gareth Halfacree...
Page 10: ......
Page 26: ...R A S P B E R R Y P I U S E R G U I D E S E C O N D E D I T I O N 10...
Page 28: ......
Page 29: ...Chapter 1 Meet the Raspberry Pi...
Page 37: ...Chapter 2 Getting Started with the Raspberry Pi...
Page 56: ......
Page 57: ...Chapter 3 Linux System Administration...
Page 79: ...Chapter 4 Troubleshooting...
Page 89: ...Chapter 5 Network Configuration...
Page 109: ...Chapter 6 The Raspberry Pi Software Configuration Tool...
Page 122: ......
Page 123: ...Chapter 7 Advanced Raspberry Pi Configuration...
Page 140: ......
Page 141: ...Chapter 8 The Pi as a Home Theatre PC...
Page 151: ...Chapter 9 The Pi as a Productivity Machine...
Page 160: ......
Page 161: ...Chapter 10 The Pi as a Web Server...
Page 172: ......
Page 173: ...Chapter 11 An Introduction to Scratch...
Page 189: ...Chapter 12 An Introduction to Python...
Page 216: ......
Page 218: ......
Page 219: ...Chapter 13 Learning to Hack Hardware...
Page 234: ......
Page 235: ...Chapter 14 The GPIO Port...
Page 249: ...Chapter 15 The Raspberry Pi Camera Module...
Page 265: ...Chapter 16 Add on Boards...
Page 280: ......
Page 281: ...Appendix A Python Recipes...
Page 287: ...Appendix B Raspberry Pi Camera Module Quick Reference...
Page 293: ...Appendix C HDMI Display Modes...