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?



I've got a machine here at work running Fedora Core 2.  Now, while I'm
turning blue waiting for the opportunity to upgrade the hardware/OS I've run
into a strange DNS self-identification problem.

Normally, I expect 'hostname' to return the FQDN of the machine
(machine1.example.com), and 'hostname -s' to return just the short name
(machine1).  It works like that on all my other machines of various
vintages.  However, in this case, 'hostname' also returns just the short
name, and this is causing some problems for things which are tied to the
full machine name.

	/u/dlevey> uname -a
	Linux rialto 2.6.10-1.771_FC2 #1 Mon Mar 28 00:50:14 EST 2005 i686 i686
i386 GNU/Linux
	/u/dlevey> hostname
	rialto
	/u/dlevey> hostname -a
	rialto localhost localhost.localdomain
	/u/dlevey> hostname -d
	example.com
	/u/dlevey> hostname -f
	rialto.example.com
	/u/dlevey> hostname -s
	rialto

	/u/dlevey> cat /etc/hosts
	# Do not remove the following line, or various programs
	# that require network functionality will fail.
	127.0.0.1       rialto.example.com rialto localhost.localdomain localhost

	/u/dlevey> cat /etc/sysconfig/network
	NETWORKING=yes
	HOSTNAME=rialto
	DOMAINNAME=example.com
	NISDOMAIN=nis.example.com
	NETWORKING_IPV6=no


What am I missing here?
 -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