DNS settings at the registrar for proper failover

I have setup my DNS entries at the registrar the following way.  What I would like to achieve is to have a proper failover not just for the web, e-mail delivery & receipts (SMTP), but also for the pop3 clients.  Could you please help me which one setting is preffered or any other suggestions:

A (Host)  
Host      Points To                            TTL
@      69.180.6.6                           1 Hour
@      24.126.181.62      1 Hour
mail      69.180.6.6                           1 Hour
mail2      24.126.181.62      1 Hour

CNAMES (Aliases)  
Host            Points To                            TTL
ftp            @            1 Hour
webmail            @             1 Hour
www            @            1 Hour
www.webmail      @            1 Hour    

MX (Mail Exchange)  
Priority      Host      Goes To            TTL
0      @      mail.sssconsulting.net      1 Hour    
10      @      mail2.sssconsulting.net      1 Hour

==========================================================
OR
==========================================================

A (Host)  
Host      Points To                           TTL
@      69.180.6.6                           1 Hour
@      24.126.181.62      1 Hour
mail      69.180.6.6                           1 Hour
mail      24.126.181.62      1 Hour

CNAMES (Aliases)  
Host            Points To                           TTL
ftp            @            1 Hour
webmail            @             1 Hour
www            @            1 Hour
www.webmail      @            1 Hour    

MX (Mail Exchange)  
Priority      Host      Goes To            TTL
0      @      mail.sssconsulting.net      1 Hour    

Any help will be greatly appreciated.
Thank you,
Salman121Asked:
Who is Participating?
 
Ted BouskillConnect With a Mentor Senior Software DeveloperCommented:
DNS round robin isn't proper fail over.  All DNS round robin is is one DNS entry with two or more IP addresses.  As each request comes in to the DNS server it rotates the IP address it returns.

If you had two servers using DNS round robin, if one server dies, then every second DNS request will go to the dead server.

Use network load balancing the DNS entries for MX et cetera are set for one virtual IP on the load balancing array.  The array is aware of when a server dies and then redirects all traffic to the available servers.

NLB in Windows is free and simple to configure and there are many hardware products that do the same thing.  If you are non-windows I am sure there is similiar offerings for Linux.
0
 
simprixCommented:
You could use DNS round robin like this. http://content.websitegear.com/article/load_balance_dns.htm. This is not true fail over. You would need a load balancer or a DNS service like DynDNS.
0
 
Salman121Author Commented:
I tested with one MX record and two IP addresses in A record as below:

MX (Mail Exchange)  
Priority      Host      Goes To            TTL
0      @      mail.sssconsulting.net      1 Hour

mail      69.180.6.6            1 Hour
mail      24.126.181.62      1 Hour

when i pinged the "mail.sssconsulting.net", it showed the first IP address, "69.180.6.6".  I brough that server down and then pinged it again.  This time it responded witht he second IP address, "24.126.181.62".  I tested with sending mail messages as well and it seems to work OK.  I just wasn't sure if this is the proper way to to setup the failover for mail server.  Any comments?

0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Ted BouskillSenior Software DeveloperCommented:
No that isn't proper fail-over.  It is DNS round robin.  Use two different client systems and execute a ipconfig /flushdns between pings while the first server is down.  Every second request will get the first server which will fail.

Round robin DNS is NOT fault tolerant.  If a server goes down, clients will get errors.
0
 
northcideCommented:
www.barracuda.com - inexpensive load balancers.
0
 
Ted BouskillSenior Software DeveloperCommented:
Once again network load balancing in Windows is free and very easy to manage.
0
 
Computer101Commented:
Forced accept.

Computer101
EE Admin
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.