Thursday, June 24, 2004 8:16 AM Jack Howarth added: > Thanks for the information on your workaround of > assigning a hostname for 127.0.0.1. However how does this > impact running remote x sessions? That is if you discover the > ip address that dhcp is assigning the machine can you still > use 'ssh -A' to run a x window program remotely on the > machine? Or does this workaround confuse that? > Jack > ps In particular on your machine can you do... > > xhost <remote_machine_running_sshd_with_x11_forwarding_on> > ssh -A <remote_machine_running_sshd_with_x11_forwarding_on> > xcalc > > ...and see the xcalc show up locally? Yes. The key is your resolver order. You should be set by default to use DNS first and /etc/hosts second. This is a function of the bind mini-resolver and not fedora. This has been the default name resolution order in every linux distro I have used to date. It has historically been done this way for the simple reason that networks go down from time to time and none of us want our hosts to stop working properly when they do. The long and short of it all is that you are perfectly safe adding an entry in /etc/hosts pointing your hostname to 127.0.0.1. Eric Diamond eDiamond Networking & Security eric<at>ediamond[dot]net
