Huawei Cloud DNS vs Amazon Route53
Introduction
Hello Everyone!
It’s me again but this time our topic is a little bit different than the first topic. This time we gonna see a comparison between Amazon Route 53 and Huawei Cloud Domain Name Service.
Let’s start with the description for both service at the both Cloud Environments
Domain Name Service description at the Huawei Cloud
Domain Name Service (DNS) is a highly available and scalable authoritative Domain Name System (DNS) web service that translates domain names (such as www.example.com) into IP addresses (such as 192.1.2.3) required for network connection. The DNS service allows end users to visit your websites or web applications with domain names.
And adds 4 basic resolutions explanation to this description
Public domain name resolution
Maps domain names to public IP addresses so that end users can access your website or web applications over the Internet.
Private domain name resolution
Translates private domain names into private IP addresses to facilitate access to cloud resources within VPCs.
Reverse resolution
Obtains a domain name based on an IP address. Reverse resolution, or reverse DNS lookup, is typically used to affirm the credibility of email servers.
Intelligent resolution
Returns different IP addresses for the same domain name based on the carrier networks or geographic locations. This significantly reduces network latency for end users from different carrier networks and geographic locations.
Amazon Route53 description at AWS
Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service.
Also AWS adds 3 functions explanations to description.
Register domain names
Your website needs a name, such as example.com. Route 53 lets you register a name for your website or web application, known as a domain name.
Route internet traffic to the resources for your domain
When a user opens a web browser and enters your domain name (example.com) or subdomain name (acme.example.com) in the address bar, Route 53 helps connect the browser with your website or web application.
Check the health of your resources
Route 53 sends automated requests over the internet to a resource, such as a web server, to verify that it’s reachable, available, and functional. You also can choose to receive notifications when a resource becomes unavailable and choose to route internet traffic away from unhealthy resources.
Amazon Route53 is routing traffic at the same way with the Huawei Cloud DNS !! Don’t believe me believe in their docs 😵
DNS Flow at Huawei Cloud
Amazon Route53 Flow at AWS
Huawei Cloud’s Resolutions
Public Domain Resolution
Private Domain Name Resolution
Reverse Resolution
Did you heard about the Lines ? One More Level Deep🤪🤪
Intelligent Resolution
ISP Lines
Usually, a DNS server returns the same IP address to visitors from different networks. However, in cross-network access, this would lead to high latency and poor user experience.
If you configure ISP lines when you create record sets, the DNS server returns different resolution results or IP addresses to visitors based on their carrier networks.
Region Lines
If you configure region lines when you create record sets, the DNS server returns different resolution results or IP addresses to visitors based on their locations.
Custom Lines
This time let’s go on from a scenario
The public zone function provides you with more than 300 carrier and region resolution lines. You can also customize resolution lines based on specific IP address ranges. Usually, a DNS server returns the same IP address to all visitors, irrespective of where they come from. Custom line resolution returns a specific IP address based on the IP address of a visitor.
You can configure custom resolution lines to obtain different resolution results based on source IP addresses of visitors.
If your website (example.com) is providing services both for external and internal users, you can configure different resolution lines so that the DNS server can return the external server address (1.1.1.1) to external users and internal server address (2.2.2.2) to internal users.
Weighted Routing
A large website is generally deployed on multiple servers. To balance the load of each server, you can use weights to control the proportion of requests to each server.
The DNS service allows you to set weights to record sets to route the requests to different servers based on the specified weights.
I’m gonna add the sources at the end for more information
If you make it until here you are excited and in my target audience 👽
Take a look at the images one more time, did you recognize?
Okay okay. Let’s dive in one more time🤪
DNS’s main aim is resolution of the name.
AWS Docs Explains DNS Resolver
Responds recursively to DNS queries from AWS resources for public records, Amazon VPC-specific DNS names, and Amazon Route 53 private hosted zones, and is available by default in all VPCs.
Let’s get in AWS a little bit and Routing Policies of it :)
Simple
- Route to one resource
- Multiple values can be defined in the same record
- If there is more than one response, client chooses one randomly
Weighted
- Routes the traffic by percentage.
- DNS record has to have same name and type
- Use cases can be load balancing between REGIONS and testing new app versions
- If we want to cut the traffic to a resource weight value must be 0.
- This policy described in Intelligent Resolution
Latency-based
- Routes the traffic which has the lowest latency
- Latency decided by users and AWS region
Failover
- Two resources are created as one primary and one secondary. If primary is unhealty then secondary resource takes the stage automatically.
GeoLocation
- Routing for user location
- If there is no routing at the location it must be created as “default”
- In Huawei Cloud its described in Intelligent Resolution
Geoproximity
- More traffic routing based on specified bias
- If resources are AWS resources AWS region must be specified
- If resources are not AWS resources there must be longitude and latitude values specification for resources.
- Must use Traffic flow(Advanced) for this option.
Conclusion
At the end what we learned in this topic?
- These services doesn’t routes the traffic they answers the DNS queries.
- Huawei kept it simple to understand DNS.
- In both provider this services workflow has a lot of similarity.
- At the detail side AWS is trying to explain more complicated situations.
- If we want to get better experience while connecting our website we should use the functions of these services.
I wanna keep it simple as much as I can for now. After my wide research I will be back with much more information and maybe a little demo for both provider. 😊😊
