I want to use my own DNS and I'm now convinced to use a second box for the 2nd DNS server (I do care about my customers emails going thru). However, the main box I have now is more than enough for my hosting needs as I'm starting out. So my questions are the following...

1) If the 2nd DNS server, for redundancy, needs to be on a different network, would I still be able have this setup?

ns1.mydomain.com (123.123.123.123) on ServerMatrix network
ns2.mydomain.com (12.23.45.00) server on another network

2) Does my 2nd DNS server have to have its own domain name so that my DNS would look like this?

ns1.mydomain.com (123.123.123.123) on ServerMatrix network
ns2.mydomain.net (12.23.45.00) server on another network

3) Since the 2nd DNS server is there for backup and mainly for emails to resolve and cache to when the main DNS goes down, can I use a DSL (don't laugh) connection for it (I know it has to be on 365/24/7, with UPS, RAID and dedicated IP, etc.)?

My idea is to host my 2nd DNS in my office using DSL connection which would place the server on a completely different network. I only have three people accessing the Internet at one time durng business hours so traffic should not be a problem in case the main DNS goes down and emails are rerouted and cached on the 2nd.

Any input, theoretical and actual experience would be greatly appreciated.

Yes

No, all DNS cares about is the A record (the IP address of the server). You can all it what you like, so your setup in question 1 is correct.


Sure, why not. I had a public DNS server on our DSL line for a while. DNS is extremely lightweight as it uses UDP rather than TCP and will require very little bandwidth.

Thanks cprompt. I guess it's time for me to tweak.

Do you have a backup MX server? If not, the moving your DNS servers isn't going to get you much. If you main box dies, your mail servers and your web server is along with it and your DNS server will be the least of your troubles.

To me, not being able to do the DNS lookup looks like the site may be gone permanently, while not being able to connect to the web server looks more like just a temporary problem.

I've also seen some Usenet server software that seems to freak out when it can't lookup a peer that it's supposed to exchange data with continuously.

-- David

Difference being is that if an SMTP client can't deliver the mail, it will schedule it for delivery later. If it can't locate the mx record because the single dns server is down, it will drop the mail straight away.

No not at this time, but I have to start somewhere and eventually, I will have a backup MX server. What I'm trying to do now is get a 2nd DNS setup on a different network and server while using all the resources that I currently have.

If the 2nd DNS stays up and is able to keep emails from being dropped (as in never to be seen again), then this is my cheapest first option or step. Next of course is to get a backup Web and MX server that takes over when the main server goes down.

Why don't you get ServerMatrix to act as a secondary DNS for your domain?

'Coz I plan to offer hosting services for others too. A namerserver that says ns1/2.mycompany.com listed in whois will serve as a simple advertising for my business.

You can map your ns hostnames over their nameserver ips... so it'll seem like yours unless someone does a reverse lookup on the ip.