Wwwizer: Solve your naked domain problem. Put 'www' in front of your domain name

Re:Wwwizer: Solve your naked domain problem. Put 'www' in fr... by samarudge on Monday January 09, 2012 @12:23PM (#3443323)

Wow, this is a terrible idea. Pointing all your domains to a service you don't control with no formal, legal contract on what they can and can't do with the domains you point at them?

[ Parent | on HN ]

Re:Wwwizer: Solve your naked domain problem. Put 'www' in fr... by dimaulupov on Wednesday January 18, 2012 @10:37PM (#3483111)

Hi! I am Dmitry Ulupov and I am running this service. You can talk directly to me at any time. My email is dima at ulupov dot com.

What a terrible idea for me would be screwing up with people websites?

Right now the service is used by more than 5000 websites and gets just shy of 10m hits a month. If anything would happen quite a few people will know who is at fault. But when any popular internet service goes down you are just getting formal apology from nobody.

[ Parent | on HN ]

Re:Wwwizer: Solve your naked domain problem. Put 'www' in fr... by dushan01 on Monday January 09, 2012 @12:33PM (#3443376)

Same as getting out of the bed every morning...

If they stop offering their service, just change your DNS record, and viola. I do not see how this could be a dangerous to you.

[ Parent | on HN ]

Re:Wwwizer: Solve your naked domain problem. Put 'www' in fr... by samarudge on Monday January 09, 2012 @01:01PM (#3443533)

With some ISP's caching DNS for >48 hours regardless of your TTL. And sometimes browsers caching pages for even longer. Stopping offering the service is fine. Ending up with your domain pointed to a site that isn't yours is an entirely different thing. They could run a phishing site and users wouldn't have any way of knowing.

[ Parent | on HN ]