• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 538
  • Last Modified:

DNS A RECORD round robin Doubt

my setup  look like this .

            Domain exmaple.com
    --- support.example.com
     ---  support.example.com
 >  nslookup  support.example.com

Name:   support.example.com
Name:  support.example.com

              This  idea  is to have backup ip  ,  any time only one  ip will  be live  .   what  will happen  when user  browse for  support.example.com  .  will it affect  performance .

3 Solutions
Premkumar YogeswaranCommented:
Hi KumarNirmal,
My Advice is to delete that back up IP from the DNS.

It can be modifed or added to DNS when ever reqired.

Using round robin in DNS it will check both the IP and connect to the client.

User 1:
Ping support.example.com
It will connect

User 2:
Ping support.example.com
It will connect

And then try with

it lacks in less performance..

please let me know if you have any question...

To avoid a performance impact I would do it like that

support1.example.com is
support2.example.com is

support.example.com is an alias DNS entry on one of those.

So from the outside world you always have the same name and with the alias you choose which server is active. The round robin idea with one 'dead end' is not a good idea.
Chris DentPowerShell DeveloperCommented:

> This  idea  is to have backup ip  ,  any time only one  ip will  be live  

You will not get that with Round Robin. Both IP addresses will be live. DNS will not check the state of the service running on that IP before handing it out to a client.


Featured Post

Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

Tackle projects and never again get stuck behind a technical roadblock.
Join Now