Debian

KVM (for Kernel-based Virtual Machine) is a full virtualization solution for Linux on x86 hardware. It consists of a loadable kernel module (kvm.ko) and a userspace component. Using KVM, one can run multiple virtual machines running unmodified Linux or Windows images. Each virtual machine has private virtualized hardware: a network card, disk, graphics adapter, etc. The kernel component of KVM is included in mainline Linux, and will appear in Linux 2.6.20. KVM is open source software.

If you hope to host a static domain name, the process is quite straight forward: find a DNS provider, pay and register, provide 2 DNS server that will contain your domain information, and that's all. This shouldn't be a problem if you have 3+ static IP, so at least 2 for DNS server plus other for normal mapping. Well, as a normal Linux system administrator, this should be part of your daily jobs.

But what will happen if you don't have static IP? The case will be more complicated since you can't provide the required 2 static DNS server for redirect, and so the domain registration can't complete.

At this moment, you may think about free DDNS service, e.g. No-IP, DynDNS and so on. BTW, usually they only provide some free domain with not friendly DNS suffix (e.g. no-ip.info, no-ip.net, etc), which usually not your cup of tea...

So how to overcome these difficulties? Just combine both DDNS (take No-IP service as example), bind9 and nsupdate together. So finally, you will have a system with:

1. Real DNS hostname. You will need this from anyone of DNS service provider; and for sure, you will able to register any name as you like if available.
2. DDNS hostname for request redirect. This is just a fake name, in order to fake DNS service provider, and point the DNS NS request to our DDNS server.
3. A Debian server that running bind9, noip2 and nsupdate. We will use the nsupdate toolkit to update our own bind9, about our current public IP. So this is a loop-back hack for bind9.

For e.g. find out what opens port 3000:

Display all PID and name of the program to which each tcp port belongs:

You run VMWare Server on Debian Linux. You start a Guest OS, and suddenly your logs start filling up:

Aug 21 12:56:11 dey kernel: rtc: lost some interrupts at 2048Hz.

Aug 21 12:56:42 dey last message repeated 1528 times

Aug 21 12:57:43 dey last message repeated 3050 times

Aug 21 12:58:44 dey last message repeated 3050 times

VMWare is being a little too aggressive about checking the clock.