In out-of-box Cyn.in Community Edition ISO CD, the default mapping is to accept *any* domain that comes to the server's IP address. So, all you have to do is point a domain of your choice from your DNS server to the IP address of the Cyn.in server and it will start to work immediately.

If you have an always-changing IP address, then your DHCP server needs to either be configured with a permanent IP address lease for the MAC address of the NIC of the Cyn.in server (again, ifconfig is your friend), or be configured to updated your DNS server with updated IP addresses, appropriately.

But what if I'm running the Cyn.in ISO Cd in VMWare? =)

The above way would work with both, virtualized as well as physical dedicated machines. Is there some confusion with "LAN" IPs, v/s the virtualization network method?

In vmware, you have to choose *bridge* mode networking, to let people outside your host computer to access it. If it's currently set to NAT mode networking in *vmware*, please change it to bridged mode and then check the IP address.

oh okay, yes i've set it to bridged mode. sorry, i am still quite confused. i hope you can bear with me.. =)
This is my current situation.. I have two separate LAN's - A and B. I would like the Cyn.in server (on vmware) to be accessible only in LAN A. We are usually connected to LAN B and to be able to connect to LAN A, we use a VPN connection. So what I did was before running vmware and cyn.in for that matter, I connect to my VPN first. Cyn.in on vmware is set on bridge mode and so it is now accessible on LAN A (via VPN of course) but only by entering the IP address.

I would like to first ask how come I cannot access cyn.in when I type the hostname which I set during the setup.. E.g. I set it to be http://kb.asia . But when I access this on my browser, it gives me an error..I believe a DNS error..

Sounds like a VPN configuration issue, are you able to resolve other host names through your VPN tunnel on LAN A?

Yup, that's a DNS error, I think you're right ericsmith.
This is a hunch, but I think you're running all this on a Windows domain that's controlled by a Windows 2003+ domain controller? :)

I think you're confusing "regular" good-old DNS with what MS provides with Windows via NETBIOS and the likes. You set up a hostname for the Cyn.in server, but your PDC (Primary Domain Controller) still doesn't know anything about that. In "normal" windows domain networking, when you setup a computer to be part of a domain, there's a whole lot of proprietary internals that goes on, that tells the PDC about the new host automagically (after you enter credentials for a domain admin, on the new computer).

Now, you get to tell your PDC about your new computer that's "not" on your domain, manually. You'll have to open up DNS management on the PDC and add a new computer to it, providing the IP address and the hostname you want to use, this will allow hostname lookup once you set it up. Further, you'll also possibly be running a DHCP server that's assigning IP Addresses leases on your LAN. If the IP Address of your Cyn.in server keeps shifting because of this, you'll keep losing the DNS mapping. To fix this, you'll have to add a permanent lease by providing the MAC address that the Cyn.in server has got on the Windows DHCP server. You can get this MAC address by logging into the command console on VMWare and typing in the "ifconfig" command. Pick up info for eth0.

Or, I'm completely wrong with my hunch, and you are in fact running a DNS server, that's not like above. Either way, the resolution remains the same - you have to add an A Host entry for the IP address of your Cyn.in server.

Lastly, unless you really are running with a domain controller resolving the domain "*.asia" controlled by you, you'll still not be able to get name resolution for kb.asia to work. You could make an entry in your /etc/hosts file (that's c:\windows\system32\drivers\etc\hosts on windows), but this is not an elegant solution because you'll have to go and do that on every computer that you want the name resolution to work.