ideas for PRO.ph development

[armstrong]

I recently acquired www.PRO.ph .

.ph being my home country's tld, I'm thinking of developing this one into my own little tld. Real .ph domains currently cost $35 per year (for plain .ph as well as com.ph domains), so maybe I can build a case for charging a minimal fee of, say, $2 per year, with a 10-year minimum. I imagine sites like:

Design.pro.ph
Models.pro.ph
Doctors.pro.ph
Lawyers.pro.ph
Advertising.pro.ph

Worth the effort, you think?

Anyone know where I can read more about DNS techniques that can let me fully delegate 3rd level domains like the ones above?

Thanks for the feedback, folks!

[yesonline]

Great domain that you may run your own .pro.ph registry

Good luck!

[armstrong]

Thanks, yesonline. That's the idea. Anyone else have experience doing something similar to this?

[NameTower]

pro is the best tld I can think of.

if .pro was smart they'd allow *.pro instead of all their stupid requirements.

forsure better than .net

Good Luck!

- Jordan

[biggedon]

All you have to do is get Hosting with unlimited subdomain capability!

as what you are proposing is only selling subdomains of "pro.ph"

which is the same as the "new.NET" namespace.

[armstrong]

Thanks, Jordan. I wonder when .pro will do a .name and offer 2nd level?

biggie, I think that it will have to be a more reliable solution than that. I was thinking of using the www.powerdns.com GPL solution to deliver authoritative lookups for my subdomains. The .tk tld uses (or used?) this solution, and it works.

pro.ph will function better than new.net domains, since my they won't need special plugins to resolve correctly. Instead, pro.ph subdomains will be functionally equivalent to the com.ph domains being marketed by the .ph registry. Unless I misunderstand the way DNS works, I think I can use something like powerdns to fully-delegate DNS authority to the subdomains. So when someone registers domains.pro.ph, he can submit nameservers to associate with this domain, and it should resolve correctly even if my own server is down, just like a real tld.

[biggedon]

pro.ph will function better than new.net domains, since my they won't need special plugins to resolve correctly. Instead, pro.ph subdomains will be functionally equivalent to the com.ph domains being marketed by the .ph registry. Unless I misunderstand the way DNS works, I think I can use something like powerdns to fully-delegate DNS authority to the subdomains. So when someone registers domains.pro.ph, he can submit nameservers to associate with this domain, and it should resolve correctly even if my own server is down, just like a real tld.

You are mistaken about "new.NET"!

There is no plugin needed to access a "new.Net" url.
One would just have to typein the full url = www.golf.shop.new.net. to view!

I could do the same an offer subdomains like "dj.96.net" or "69.96.net"

Checkout 20megsfree.com, perfect example of what you have in mind, only they offer subdomains free. Mine was > chitown.20megsfree.com

[armstrong]

But new.net sites don't advertise their full url, so its mostly only domain-savvy people who know about the full url. Therefore a plugin would indeed be required for a new.net domain. You can't compare golf.shop.new.net to golf.pro.ph because the former is a fourth-level domain while mine is a 3rd level

I could do the same an offer subdomains like "dj.96.net" or "69.96.net"

Of course you can, as can 20megsfree.com in your example. But will these be as marketable as dj.pro.ph? 96.net and 20megsfree.com subdomains you'd have to give away for free, while with a little branding and local marketing, one can actually sell pro.ph domains.

[.com.net.org]

subdomain service is the best.

[seeker]

a very interesting idea.
but what about when your subdomainer wants a subdomain?

i.e.

company.pro.ph

then I want, manager.company.pro.ph
ceo.company.pro.ph
ganitor.company.pro.ph

it gets a little confusing.
thats where the new.net people got it right by using their plugin (about the only thing they did right, so far)

[KING dot NET]

I recently acquired www.PRO.ph .

.ph being my home country's tld, I'm thinking of developing this one into my own little tld. Real .ph domains currently cost $35 per year (for plain .ph as well as com.ph domains), so maybe I can build a case for charging a minimal fee of, say, $2 per year, with a 10-year minimum. I imagine sites like:

Design.pro.ph
Models.pro.ph
Doctors.pro.ph
Lawyers.pro.ph
Advertising.pro.ph

Worth the effort, you think?

Anyone know where I can read more about DNS techniques that can let me fully delegate 3rd level domains like the ones above?

Thanks for the feedback, folks!

That was a good idea for .ph ... check www.referrer.com and send me pm if you are interested. I have different domain names that provides subdomain service...

Good luck to you .. btw, I owned media.ph, men.ph, cash.ph, and more... currently using PPC search engine from www.submithits.com.

Good luck again,
TheWatcher

[armstrong]

Thanks, TheWatcher. PM sent. d

[theparrot]

Thanks, Jordan. I wonder when .pro will do a .name and offer 2nd level?

biggie, I think that it will have to be a more reliable solution than that. I was thinking of using the www.powerdns.com GPL solution to deliver authoritative lookups for my subdomains. The .tk tld uses (or used?) this solution, and it works.

I would use either bind or djdns.

pro.ph will function better than new.net domains, since my they won't need special plugins to resolve correctly. Instead, pro.ph subdomains will be functionally equivalent to the com.ph domains being marketed by the .ph registry. Unless I misunderstand the way DNS works, I think I can use something like powerdns to fully-delegate DNS authority to the subdomains. So when someone registers domains.pro.ph, he can submit nameservers to associate with this domain, and it should resolve correctly even if my own server is down, just like a real tld.

It is not true that it will still resolve correctly even when your server is down, there are for example 13 root name servers for .net and .com, this is to distribute them globally, and to make sure that if some go down, or even whole network segments reaching them do, others are still reachable. To do this you will need at least four servers, on completly different major networks for reliability. If you want a tech partner let me know

[armstrong]

Thanks for the offer, theparrot. Currently, the best low-cost solution I can think of is zoneedit.com, which lets you have as many additional nameservers for a few dollars each, per year. Only thing with zoneedit is I can't define NS records, so can't fully delegate the domains.

I'm sure when this project outgrows this initial solution, then I'll be calling on you.

[KING dot NET]

Your other option is to use everydns.net service. Though I myself preferred to use powerdns service.

TW