Well, I'm trying to figure out how to build a co.cc clone. I do have some basic PHP programming experience, so I guess this is going to be something of an exercise. The question is which DNS server would you choose. I'm thinking of MyDNS, but I would love to find different opinions. thank you
co.cc isn't a site, so I don't know what you want to create a clone of. As far as a DNS server, I'd use an existing service. (If you mean a clone of the cc top level domain, you can't just "create" a top level domain.)
I guess I haven't been clear. Sorry for this. CO.CC used to be a service that provides free third level domains - yourdomain.co.cc. It was not just redirection. You used to be able to set DNS servers for your third level domain name and actually point your subdomain name to your web hosting account. The CO.CC service and site both died a couple of weeks ago. There are other live services, similar to CO.CC. An example big one is UNI.ME. Such free subdomain services tend to grow rather fast. So, that's why I was asking about a suitable DNS server that could handle such stress.
I understand. And I don't think you want to set up a public server if you "have some basic PHP programming experience". For instance, are you running on a generator that has an on-site fuel supply that will last at least 5 days? Do you have an off-site server (preferably at least a few hundred miles away) ready to switch to at a moment's notice, day or night? One really large storm (and weather on this planet seems to be getting worse every year) and your entire operation is offline for days. Or longer. Setting up a public server site is an entire specialty, not something that someone with a little programming experience should attempt.
I don't mean offense, but it is hard to achieve greatness with that sort of thinking I'm not sure that I would launch the service at all. The challenge is to build it, and to put a relatively solid base at the bottom. I mean, it's boring to learn programming just for the code. You need a project to make research for and solve actual problems. Indeed, if the service goes live, then it will need the data replicated at at least two other places, plus an off-site backup. When the service grows, it would require a whole team to deal with abuse complaints, server management, DDoS attacks, and a whole universe of unimaginable PITAs. For now I'm just gathering information how to build such a system. I have my day-time job and some spare time. It's cold outside and I prefer to keep my arse close to the heater, putting this spare time into some good use, such as learning new stuff through trial and error
There are tons of subdomain scripts. The real problem comes in the monitoring since people who spam and use malware flock to free subdomain services. Anyway, there is little reason to reinvent the wheel ... search around here, or anywhere, and you will find scripts that already do what you seek.
It's boring to learn any subject you don't want to learn, just for the subject. Many of us don't consider learning "just the code" the least bit boring. Code is just a tool, not a method. The method is called "programming", and you learn that as a totally separate subject. If you're learning "code" to learn how to write programs, the problem isn't that it's boring to learn code just to learn the code, it's that you're studying how hammers are made to learn carpentry. Learning code isn't learning programming.
Thank you for taking the time to write in this topic. I'm not a native English speaker and I don't feel strong enough to discuss semantics. Well, it is not a standard subdomain script. Indeed, there are many scripts which can apply simple redirection for subdomains. However, I managed to find just a couple that provide the option to set nameservers and DNS records for the chosen subdomain. Both of them cost a few thousands. The popular one is the script that drives the uni.me site. That's why I'm trying to build one on my own, just for the fun of it.