* Free DNS Hosting

Ours are on KVM as well but i'm going to likely have to move the resolvers off powerdns since it simply can't keep up. I know Shaw uses PDNS for their resolvers but it's quite possible that they have

For a dns cacher I have used pdnsd and it uses a joke of ram.

I was having a lot of slowness running DNS servers in OpenVZ as resolvers, so while those are still there, they are just doing authorative DNS now, and moved to caching resolvers in KVM and stuff is l

600MB Ram for a DNS server? WOW, We are using one called Simple DNS Plus and its currently using 278MB... Maybe an upgrade is in order? (Image)

Running a caching DNS server can eat up quite a bit of RAM & CPU. Ours is doing 600M RAM and a full core :P It's a case of damned if we do, damned if we don't. For a while we simply just used

I think if 20-30 ms is an issue for some people, they can install their own DNS cacher. Or, maybe you can suggest using your resolvers for the people that needs it (IMHO almost nobody). I like the goo

Hmmm I got it. Fran, why to use your nameservers for the our VPS's? Public dns is fine IMHO. But, this isn't the issue on thiei thread :P

The SSH slow down was because our main resolver went bonkers and resolver02 didn't pickup (i hate power-dns sometimes (Image)

I have the DNS problem, and seems that dropbear doesn't have a setting to fix this, unfortunately

* Free DNS Hosting

Fully redundant DNS service available

I can see that my ISPs DNS seems to be playing up as always, need to get that fixed before anything.

I am going to do so, nothing has been changed yet. They are all pointing to my DNS cluster, ns1-5.infinitymedia.org.uk are my box's.

I think I misunderstood it earlier, did you mean you've changed ns1 & ns2 at your registrar for your domain name, into another DNS service like HE (or into NSD hosted at another box)?

Restart the vps which has the dns service running, it's one of the solution's for these crazy errors :-P

It's better to just focus on one domain, if one domain hosts the DNS and uses it's own nameservers, then try to get it working alone and once it's working correctly, you can then add it's nameservers

Well...quite a bit of "almost". If one of your boxes is down for a period of time, you're relying on the DNS TTL which is at the mercy of what ISPs and browsers honor. It's better th

-Debian minimal template has things like Apache, DNS, Samba but a quick run of the LEB debian bootstrap fixed that right up.

Hmm.. I'm a little more sane now! I've just remembered that the VPSs I tested with are the one's that host the DNS anyway so.. but that doesn't explain pingdom.