On 10/4/19 1:36 PM, Dan Ritter wrote:
> Please show us:
>
> /etc/hostname
root@pix:~# cat /etc/hostname
sbox
> /etc/hosts
root@pix:~# cat /etc/hosts
# /etc/hosts: This file describes a number of hostname-to-address
#
# Host Database
# localhost is used to configure the loopback interface
# sudo cp hosts /etc ; dist `pwd`/hosts /etc all hosts
# The following lines are desirable for IPv6 capable hosts
# when the system is booting. Do not change this entry.
#
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
127.0.0.1 localhost.localdomain localhost lh lcl
# misc ne'r-do-wells
127.0.0.2 ad.doubleclick.net
127.0.0.2 mmv.admob.com
# Pasadena
206.135.251.11 rrserv.richeyrentals.com rrserv rrrc rrc
# an indra IP (net.indra.com)
209.169.1.5 net.indra.com indra nic
# a FRII IP
216.17.135.75 www.frii.net frii
# Debian mirrors
184.105.204.138 mirror.picosecond.org mpo pico
128.135.10.29 punk.uchicago.edu
169.229.226.30 mirrors.ocf.berkeley.edu
128.30.2.26 ftp.us.debian.org
128.61.240.73 security.debian.org
# RPi mirrors
93.93.128.193 raspbian.raspberrypi.org
169.229.226.30 mirrors.ocf.berkeley.edu
# DHCP range -- no longer operative
# 192.168.3.225
# ||||||||||||
# 192.168.3.250
# /30 IPs from FRII (I'm pretty sure)
# their end (my default)
216.17.129.42 fromFRII.net fromFRII fFn
# my router IP
216.17.129.41 toFRII.net toFRII tFn
# tmp
216.17.134.204 rrservCO.slsware.net rsn
# FRII net (at Frasier with a bare router -- 202, 205, 204, 206 are dioded)
216.17.134.200 slsware.net
216.17.134.201 outgoing.slsware.net outgoing osn
216.17.134.201 brouter.slsware.net bsn
216.17.134.202 srv.slsware.net srv ssn
216.17.134.202 mail.slsware.net mail msn
216.17.134.202 www.slsware.net www wsn
216.17.134.202 ns1.slsware.net ns1n
216.17.134.202 ntp.slsware.net nsn
216.17.134.203 gobook3.slsware.net gobook3 gb3 gb
216.17.134.203 gobook2.slsware.net gobook2 gb2
216.17.134.204 test.slsware.net test t
216.17.134.205 sbox.slsware.net sbox
216.17.134.206
216.17.134.207
# LAN using 216.17.134.?/24
216.17.134.5 printer.slsware.net printer 4240
216.17.134.23 bridge.slsware.net bridge br
# some temporary Juniper stuff
192.168.1.1 ssg.slsware.net ssg fw
192.168.2.1 ssgadmin.slsware.net ssga fwa
# netgear wifi AP
192.168.1.1 www.routerlogin.net netgear ap AP
> the output of
>
> hostname -f
root@pix:~# hostname -f
hostname: Name or service not known
> hostnamectl
root@pix:~# hostnamectl
Static hostname: sbox
Transient hostname: pix
Icon name: computer-desktop
Chassis: desktop
Machine ID: d01c1f97efc944bd81768d849446feaf
Boot ID: 50e006fce53c47a881b78f09c0bbcbe2
Operating System: Debian GNU/Linux 10 (buster)
Kernel: Linux 4.19.0-6-amd64
Architecture: x86-64
Hmm. That's interesting. Transient hostname. I didn't know of
hostnamectl. Tells what it is, but not what to do about it or where it
came from.
--
Glenn English
