We're looking at SimpleDNS - hoping it will be more robust and stand up to the spamfilter.

 

Anyone use Simple DNS Plus or have comments on what you do use?

 

thanks

jerbo128

 

Another nice feature is if you have 2 of them and create a new record on the primary it will create the account on the secondary automatically as well as keep it in sync. So all you have to worry about is 1 DNS server and the slave will mirror the master.

jerbo128,

 

How many messages / minute do you have that MS DNS can not handle it?  I have what I feel is fairly high traffic and have zero issues with DNS.  I have 2 MS-DNS resolvers and 1 BSD and a backup.

Desperado -

We average 30-50 connections at a time to the SFE.  I am checking 5 MAPS and 2 SURBL Lists, plus reverse dns, mx, spf, etc.

 

When it fails, the service remains running, but I get a lot of timeout, or dns server reports query errors.  I had a batch file setup to restart the dns service every hour, and that helped alot.  But it was still something that I had to keep an eye on.

 

I liked the idea of SimpleDNS due to the fact that WebGuyz stated above:  you add a domain to the master and it sends it to all slaves.  That is a huge timesaver.

 

We did switch to the simpleDNS trial, and after 48 hours of running it, have not had to restart it at all.  It is showing 30-40 queries/sec with spikes to 70.

 

I guess our setup is not the same.  We do not have ANY zones on our resolvers.  They are used for our servers to do DNS lookups only (Caching Servers) so I am comparing Apples and Oranges!

 We tried the forwarders once before, and found that it was much more efficient to just resolve the domains ourselves.   It created a lot of timeouts in the SF.

 

So far, I am thrilled with the Simple DNS.  The GUI alone is so much better.  Not to mention the performance.

 

We ARE an ISP and do not use forwarders.  Our resolvers (caching DNS servers) look directly at the root servers.

 

  Was replying to jerbo128, I should have been more specific. 

 

Some smaller shops still use their ISP's DNS but with the load caused by RBL and SURBL lookups they might start getting resource limited by their ISP's.

 

 

 

You update NS1's records, click Tools, reload DNS records and then all 3 get sync'd. Never have had any issues with crashing and I mean never. Had issues with NAT where our main NS server was on the internal network and workstations would look to it for records of websites we host and get returned the external IP which of course doesnt work. Simple DNS added a feature not too long ago that allows you to map an external IP to an internal IP. Pretty cool. So most of our website reside on the same external ip and internal ip, so one simple nat map fixed that problem.

 

My NS1 Simple DNS reports uptime 183 days  12,972,858 Requests.  Judge for yourself if thats stable :)

 

 

 

IKILLSPAM1,

 

In cases like this, which are common especially in co-locations where the IP's are private inside, your firewall should do "DNS ReWrite" which globally solves this issue.  In the case of Cisco PIX firewalls, you can do DNS ReWrite on a rule by rule basis.