GNU/Linux Desktop Survival Guide by Graham Williams
Desktop Survival Project Home Preface Advocacy History Distributions Installing GNU/Linux Basic Survival Wajig Applications AI, Machine Learning, Data Science Android - GNU/Linux Devices Audio Backup Booting CD Chinese ChRoot Clock Command Line Databases DIA Directories Disks EcoSysL Emacs Email Evolution Files File Systems Firewalls Floppy Disks FreedomBox Glade GNOME Graphics, Images, Photos Hardware Initialisations on Booting Installation Examples Internet IOT Java KDE Kernels Keyboard Konqueror KVM Switch LATEX Log System Login Magellan MATE Mathematics Memory Modems Mounting Devices MS/Windows Music MySQL Nautilus Networks Nextcloud Network File System NFS NT File System Oracle Packages Partitions Passwords PDF Power Management PPP Presentations Printing Python R Remote Desktops Rsync Samba Scanning Science Screens Security Spreadsheet SSH Swap Teradata Data Warehouse Themes TV Unity USB Version Control Video Virtualization Voice over IP WebCam WordPress Web Sites Word Processing and Printing X XML Troubleshooting Index

CLICK HERE TO VISIT THE UPDATED SURVIVAL GUIDE

ADSL and DNS Debugging

In my setup Internet connections are sometimes apparently slow and sometimes fail DNS lookup. The problem turned out to be because the default /etc/resolv.conf used the ADSL Modem/Router as the DNS (and this file was updated automatically at around 9:30am each day to):

  search
  nameserver 192.168.0.1
  nameserver 0.0.0.0

Changing it back to:

  nameserver 203.0.178.191

fixes the DNS problems. The router seems to correctly identify the DNS itself (203.0.178.191) but somewhere things don't work. This is overridden in /etc/dhcp3/dhclient.conf by adding the two lines:

send host-name "athene.togaware.com";
supersede domain-name-servers 203.0.178.191;

Perhaps the router is smart enough to do local DNS with athens mapped appropriately? If so, then don't need the static (but possibly changing) entries in /etc/hosts.