software lock-in

[RShadow]

I'm interested in signing up for your service, however I have some questions.

1. I noticed some screen shots showing the setup of reverse dns. Does this mean that I am locked into a specefic DNS server? I can't stand BIND and I would much rather use djbdns.

2. This brings me to number two. I enjoy using apt-get, yum, emerge or whatever to keep the majority of the system up to date, however certain applications I like to maintain and update myself (djbdns, httpd, php, qmail, courier, etc). Do your OS images have a working (and updated) toolchain. Is this allowed?

3. Firewall. I prefer to manage my own firewall... are your virtual servers locked behind your own firewall (It doesn't really matter if I have access to change it or not). My current provider has me locked behind there firewall. I have a spiffy interface to make changes, however that doesn't do a lot of good when I am running applications that need to make changes to the firewall dynamicaly (swatch, snort, etc).

4. I noticed in the instructions you say that you can compile your own kernel modules, but you can not compile your own kernel? If I have access to the filesystem why can't I can compile my own kernel and place it in /boot and reboot the server? If Xen requires a certain patch-set to function, its not really difficult to apply that patch-set myself.

Thanks for any answers I may receive.

[matta]

Hi,

1) The reverse DNS section of Teknic is only for the reverse resolution of your IP address(es). You are free to run whichever DNS server you like on your server.

2) All the distros come with their standard tools such as you mention. You can use them, compile from source, whatever... you have root, it's just like a regular server.

3) You have full iptables support, even state, nat, raw tables, QoS, etc. I don't think we have ebtables/IPv6 iptables compiled by default, but you can compile the modules for them if you want.

4) With Xen the kernel is loaded on the host server, it doesn't have a boot loader for the VM's so it doesn't matter what is in your /boot. Over the next couple of months I do expect to have a boot loader in place to allow users to boot their own kernels.