irgeek wrote:
Nope. Once DNS is pointed to you all DNS is pointed to you. Of course, having only one DNS server means that if your linode dies, DNS dies with it. Since everything is on the same machine, that may not be a problem becasue DNS is pretty useless if all the services it points to are down.
Yea for right now that is my thought. DNS does no good if the service is not running.
irgeek wrote:
As for slow queries, how is the DNS server started? If it's starting as a service that runs on it's own, I don't know what to tell you. If it's started by something like inetd each time there's a query, the startup time would explain the lag. In that case I'd say figure out how to start it as a service.
I figured it out. It has something to do with my home setup. Either it is not getting cached by my ISP or my ISP is real slow. I pointed my resolv.conf to my DNS server and it goes fast. So I know my server is responding quickly. I have also tested at other locations and it resolves quickly.
Quote:
One more thing. Given your domain name I'm guessing that you'll be running a hosting service off your linode. Might I suggest that you'd be well advised to get a second linode (preferably in the other datacenter) that mirrors the current one for failover purposes. People don't like when something happens to their precious web sites. Just a thought.
Yea I am just kind of getting started now. I have 4 sites that I was hosting on phpWebhosting for $10 per month. phpWebhosting was good to me but I wanted more control. I saw I could get a linode for $20 per month and have my own server. I figured I could get more control and save $20. If I get enough people I will start adding some redundency but right now it provides "enough" reliability for the people I am hosting. In the end it is just something on the side. Not really a "real" webhosting company (yet). The people I host know this and accept this.
Thanks for your help and advice.