Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That is not particularly rational. It makes moving hosting providers harder and many provide very different dns services. You might want an api or support for different record types that otherwise good hosting services dont provide. I use zerigo just for dns because they are really goid at it...


Managing DNS completely separately is fine, too. I just don't think it's a particularly good idea to use your registrar as your DNS provider unless you're also using it for hosting. I'd much rather point my registrar at my host's DNS than to have to update DNS records every time something changes on the host.


> have to update DNS records every time something changes on the host.

On the other hand, you might want to be able to do that rather than not be able to.

I'm thinking of the situation where your host goes down. If it is host-wide, your (their) DNS servers might be down too.

I intentionally use a different company for DNS than hosting, so if the host goes down I can point my DNS to somewhere else.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: