Finally the help of IT is here

Blog of computer solutions.

How to create an external dns server with Amazon Route 53

Written by Xaus Xavier Nadal on December 9th, 2014

Save pagePDF pageemail pagePrint page

Create an external dns server with Amazon Route 53 is as simple as having Amazon AWS account and follow the steps below will show you, but first of all, what is Route 53 and what is Route53?

Amazon Route 53 It is a DNS service in the public cloud.

Amazon Route 53Amazon Route 53 normally used to do load balancing (ELB) between instances EC2, mapping instances EC2 or to simply map buckets S3, but we in this article we will use the power of a DNS Cloud for securing our environment, for have a scalability in such a sensitive service like DNS and provide high availability.

But Amazon Route 53 goes further and leaves us the possibility by Health Check to monitor the life and performance of our Web applications, for example if you have 2 instances EC2 (web server) and one of the webs stops we operate can by Route 53 immediately redirect traffic to another instance to continue offering service.

It also leaves us the possibility to buy domains (Although as personal comment I would like more extensions were available and better prices). But you know that when closer the DNS server, the domain web server fewer hops should make a customer and better latencies have to open the web before the competition always remember the good practices of SEO.

Benefits of having a DNS server on the public cloud as a service.

1.- not affected by viruses (In the absence of an operating system controlled by us is safer by definition).

 

2.- No system updates (We saved maintenance).

 

3.-No failures have 0-day in Microsoft Windows.

 

4.- And as I said the CTO of NASA "We rely more on Amazon than in our own infrastructure for securing our systems".

 

5.- Operating costs tend to 0.

 

6.- The cost of mounting an instance EC2 t2.micro is like riding 27 areas (domains) on Amazon Route 53.

How to create a direct DNS zone with Amazon Route 53

As mentioned earlier in this article we have a user account created in Amazon AWS.

And as always we must first ensure that the costs of this service do not exceed the estimate for our organization: http://aws.amazon.com/route53/pricing

Access our Amazon AWS account to manage this service is not necessary to select a region as this service is Global.

Route 53

Click on the icon Route 53 within the services page Amazon Web Services.

Create DNS on Amazon Route 53

As this article only want to show how to create a public dns server click on the Get Started Now DNS Management.

As DNS Create Route 53 Amazon

click on Hosted Zone Create

Create DNS zone on Route 53

click on Hosted Zone Create

Create DNS Zone on Amazon Route 53

We write the domain name (zone) in the field Domain Name and selected in the Type field if you want it to be a zone (domain) public or private for a VPC (Tunnel connectivity between headquarters and Amazon).

For our purpose we selected Hosted Public Zone and click on Create.

Route zone created in 53

We have our direct area created in Cloud, only now we would create the records within this area

For all this to work from the internet, we tell our ISP (Where to buy the domain if we did on Amazon) that our nameservers are those who see in the image ns-1780.awsdns-30.co.uk, ns -1019.awsdns-63.net, ns-1035.awsdns-01.org and ns-311.awsdns-38.com, as you can see different root domains are distributed in 4 highly available DNS servers.

just click on Go to Record Sets

Create Record www Amazon

To make a practical example we will show how to create the record "www" to point to the public ip of our web server.

We write in the Name field: www

Type: select A - address IPv4

We write in the Value field: <Ip public web server>

Routing Policy: By default Simple -> <'ll Discuss later in this article the different options>

click on Create.

If you have already changed your NS (Name Servers) you can check www. <Vuestrodominio> and responds with the ip you have written in the Amazon Route 53.

Different policies in public DNS Routing with Route 53 Amazon.

Simple:

This is the default and such other records within a normal DNS. The name reflects the ip that noted in the record.

Weighted:

This value is like making a Round Robin in the DNS but with weights, ie have the same name dns pointing to several IP (This is the usual round robin - to distribute the load between different destinations alternating between one or the other, and if one does not respond simpre goes to another ip or ip's) and with this policy routing also got put weights (priorities) to the records so that for example if we know that a destination server has more resources than other than this first one is the most weight has and that it receives more requests or connections.

 

In this policy we can associate a Health Check with which we get that if a server or service (What's Hot) falls map the ip from another server. (Personally I loved this option) is like having a NLB but directly in the DNS. We recommend that if ye use this option will bajéis the time to live (TTL) to 60 seconds or less as required.

Latency:

With this value we get that registration respond basing in regions that specify and latency that are from either instancoa, I explain (It would be like having a CDN but server) that is, that according to which country we are performing the motion a instance located in a certain region will better times another and therefore will point to a DNS EC2 instance preferably the same software resources located different regions.

 

When we talk about web servers is easy to imagine a similar scenario, but if we think replicated data servers if 2 servers have identical data repositories with the same one located in Tokyo and another located in Barcelona, ​​this policy got send to customers Barcelona Barcelona server and client server Tokyo Tokyo improving customer response time from the server.

 

We can also do as in the previous case to redirect to another server in the event that the service we have defined in Health Check unresponsive.

Failover:

This policy is only used in public areas and simply sends the request to a destination or another in case one is not available.

Geolocation:

This policy is useful when you want to improve web positioning, with this option we manage to answer a server or another depending on where the customer is saying is that if you are located geographically in Ireland DNS point to Ireland if we have well defined. We get thus provide a response to the client from the nearest area geographically him. For this we have servers in different geographic areas of course.

 

We can also do as in the previous case to redirect to another server in the event that the service we have defined in Health Check unresponsive.

Greetings and see you soon MegaCracks.

Related Posts Plugin for WordPress, Blogger ...
Tags: , , , ,


One Response to "How to create an external dns server with Amazon Route 53"

  1. jabama Says:

    if I have a .in domain miempresa.mx, with that kind of dns I have to aim it?

Leave a Reply

XHTML: You can use in Original tags: <a href="" title=""> <abbr title = ""> <acronym title = ""> <b> <blockquote cite = ""> <cite> <code> <del datetime = ""> <em> <i> <q cite = ""> <s> <strike> <strong>