Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

An odd DNS conundrum?



On Tue, 2006-12-19 at 11:57 -0500, Matthew Gillen wrote:
> Don Levey wrote:
> > 	/u/dlevey> cat /etc/sysconfig/network
> > 	NETWORKING=yes
> > 	HOSTNAME=rialto
> 
> John's right.  The HOSTNAME line should have your FQDN.  You might want to
> delete the DOMAINNAME line too.
> 
> > 	DOMAINNAME=example.com
> > 	NISDOMAIN=nis.example.com
> > 	NETWORKING_IPV6=no
> 
> Matt

That seems to have done it - FQDN in HOSTNAME.  Previously, I had no
DOMAINNAME setting and 'hostname -s' gave me 'localhost' so I guess I
needed that one too.  I wish I know why, after almost a continuous year
of uptime, things started going south now.
 -Don

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org