Roger, thanks

, wait does my site need to be on the computer for it to work?
==========================
The old, easy way to do this is with a hosts file. These are a unix-ism really, but exactly the same format is used on most Windows and OS/2 systems, thankfully.
Where is it?
On unix: /etc/hosts
On Windows 95: windowshosts
On Windows NT4: winntsystem32driversetchosts
On OS/2: MPTNETChosts (depending on your ETC environment variable)
What does it look like?
On my local network I have three machines:
penfold at address 192.168.1.1
dangermouse at address 192.168.1.2
taz at address 192.168.1.4
(the perceptive amongst you will have spotted that these are private addresses - yep, it's a private network with penfold as the gateway. But that's not important right now...)
So on all three machines (one runs Linux, the others boot between 95,NT & Linux) the hosts file looks like this:
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server. Just add the names, addresses
# and any aliases to this file...
#
# For loopbacking.
127.0.0.1 localhost
192.168.1.1 penfold.blighty.com penfold
192.168.1.2 dangermouse.blighty.com dangermouse
192.168.1.4 taz.blighty.com taz
Anything beginning with a '#' is a comment.
The format is an IP address, followed by a list of hostnames.
If I want to connect to penfold I can use any of
telnet 192.168.1.1
telnet penfold
telnet penfold.blighty.com
..they're all equivalent.
This is fine for a network of a few hosts, but for anything bigger you need a more distributed system...
=================
is this how would you do it? I don't know, right now I can't log into my server cause i'm at work

.