(Resend. Accidentally sent to a human instead of to the list...)
> On Nov 11, 2016, at 11:45 PM, Andy Smith <a...@strugglers.net> wrote: > > Okay. So I think we should focus on why "hostname -f" returns the > wrong/outdated info. I'm not sure yet. > > Out of interest what does "hostname -d" return? slsware.dmz (Wrong) > Should be just the > domain name part It is. Of the wrong FQDN. > And what is the contents of /etc/hostname and /etc/hosts? cat /etc/hostname: srv (Right) This is what plain hostname returns, and this is the CLI prompt, too. But hostname -f claims the hostname is 'www'. Must be coming from different places. /etc/hosts, see below. > I'm assuming you have actually rebooted at least once after changing > /etc/hostname and /etc/hosts, yes? At least once. But I didn't change /etc/hostname -- nothing wrong with it. -- Glenn English > # 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 localhost.localdomain 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 rrrc rrc rrserv > > $ an indra IP > 209.169.0.5 indra.net indra inc > > # a FRII IP > 216.17.135.75 www.frii.net frii > > > # pass I slsware.org -- all routable IPs; no NAT > 216.17.203.64 slsware.org > 216.17.203.65 out.slsware.org oso > 216.17.203.66 srv.slsware.org sso > 216.17.203.67 gobook.slsware.org gso gbo > 216.17.203.68 unused0.slsware.org u0so > 216.17.203.69 unused1.slsware.org u1so > 216.17.203.70 printer.slsware.org pso > 216.17.203.71 broadcast.slsware.org bso > > > # around the router > 192.168.0.5 brouterloopback.slsware.per brouterloopback blsp blo > 192.168.0.9 brouter2.slsware.per brouter2 b2sp > > # perimeter boxen > 192.168.1.1 brouter.slsware.per brouter bsp > 192.168.1.2 firewall.slsware.per fsp pixp > > 192.168.1.3 1721.slsware.per lrsp lsp > 192.168.1.4 gobook.slsware.per gsp > > # .net DMZ > 192.168.2.1 firewall.slsware.dmz fsd pixd > > 192.168.2.150 rpd0.slsware.dmz rpd0 > 192.168.2.151 rpd1.slsware.dmz rpd1 > 192.168.2.152 rpd2.slsware.dmz rpd2 > 192.168.2.153 rpd3.slsware.dmz rpd3 > > 192.168.2.201 outgoing.slsware.dmz osd > 192.168.2.202 ns2.slsware.dmz ns2 > # 192.168.2.203 srv.slsware.dmz srv > 192.168.2.203 www.slsware.dmz wsd srv > 192.168.2.203 mail.slsware.dmz msd srv > 192.168.2.203 ntp.slsware.dmz ntp srv > 192.168.2.203 ns1.slsware.dmz ns1d ns1 srv > # 192.168.2.204 server.slsware.dmz ssd > 192.168.2.205 log.slsware.dmz lsd > 192.168.2.205 ns0.slsware.dmz ns0 lsd > > 192.168.2.9 gobook.slsware.dmz gsd > > # virtuals > 192.168.2.203 www.bouldermedicaladvocate.com bma > > # LAN > 192.168.3.1 firewall.slsware.lan fsl pixl > > # DMZ on the LAN 192.168.3.150..55 > # the unused rpi mark3B > 192.168.3.150 rpl0.slsware.lan rpl0 > # the piPile -- .151 is 1 3B, the others are 2Bs > 192.168.3.151 rpl1.slsware.lan rpl1 > 192.168.3.152 rpl2.slsware.lan rpl2 > 192.168.3.153 rpl3.slsware.lan rpl3 > # the HP/3.5" screen > 192.168.3.154 rpl4.slsware.lan rpl4 > # the main sls server > 192.168.3.155 supermicro.slsware.lan sml sm5 > > 192.168.3.2 timecapsule.slsware.lan tsl > 192.168.3.3 lanserver.slsware.lan lsl > 192.168.3.4 > 192.168.3.5 4240n.slsware.lan 4240 printer > 192.168.3.6 maxi.slsware.lan maxi msl > 192.168.3.7 > 192.168.3.8 > 192.168.3.9 gobook.slsware.lan gbl > # 192.168.3.10 gobook wifi (below) > 192.168.3.11 > 192.168.3.12 sbox.slsware.lan sbox ssl > 192.168.3.13 > 192.168.3.14 lmaxi.slsware.lan lmaxi lmsl > 192.168.3.15 > 192.168.3.16 air.slsware.lan air asl > 192.168.3.17 mini.slsware.lan minisl > ; > 192.168.3.22 se30.slsware.lan sesl > 192.168.3.25 tv.slsware.lan tvsl > 192.168.3.26 bd.slsware.lan bdsl > > # Juniper firewall - WAN > > # Juniper firewall - DMZ > > # Juniper firewall - LAN 192.168.3.50..59 > 192.168.3.50 ssg50.slsware.lan ssg0 > 192.168.3.51 ssg51.slsware.lan ssg1 > 192.168.3.52 ssg52.slsware.lan ssg2 > 192.168.3.53 ssg53.slsware.lan ssg3 > 192.168.3.54 ssg54.slsware.lan ssg4 > 192.168.3.55 ssg55.slsware.lan ssg5 > 192.168.3.56 ssg56.slsware.lan ssg6 > 192.168.3.57 ssg57.slsware.lan sgui ssg7 > 192.168.3.58 ssg58.slsware.lan sdmz ssg8 > 192.168.3.59 ssg59.slsware.lan slan ssg9 > > # WiFi > 192.168.3.10 gobook.slsware.wif gbw > 192.168.3.101 ipad.slsware.wif psw > 192.168.3.102 kindle.slsware.wif ksw > 192.168.3.150 rpw0.slsware.wif rpw0 > 192.168.3.151 rpw1.slsware.wif rpw1 > 192.168.3.160 air.slsware.wif asw > 192.168.3.170 mini.slsware.wif minisw > 192.168.3.190 itouch.slsware.wif isw > 192.168.3.200 gphone.slsware.wif gsw > 192.168.3.210 iphone.slsware.wif isw > > # DHCP range > # 192.168.3.224..31 > # |||||||||||| > # 192.168.3.231 > > # /30 IPs <> FRII > # their end (my default) > 216.17.129.42 fromFRII.net fFn > # my router IP > 216.17.129.41 toFRII.net tFn > > # slsware.net > 216.17.134.200 > 216.17.134.201 outgoing.slsware.net osn > 216.17.134.202 ns2.slsware.net ns2n > 216.17.134.203 srv.slsware.net ssn > 216.17.134.203 mail.slsware.net msn > 216.17.134.203 www.slsware.net wsn > 216.17.134.203 ns1.slsware.net ns1n > 216.17.134.203 ntp.slsware.net nsn > 216.17.134.204 server.slsware.net serversn > 216.17.134.205 log.slsware.net lsn > 216.17.134.206 > 216.17.134.207 (FRII is my ISP. 216.17.203.66 in the pass I slsware.org list is the server in question. per is the local perimeter network. com and net are nets from my old location -- they're mine, but I'm working with org in hopes of avoiding confusion. I'll be somewhat embarrassed, but quite grateful to hear that a config error in this is causing my troubles...)
