Route53 (R53) Fundamentals

Ki Route 53 aur DNS exactly same cheez ne?

Nahi. DNS ek universal protocol/concept Aah, jabki Route 53 AWS da ek specific product/service Aah jo DNS protocol nu use karda Aah aur advanced features dinda Aah.

Scenario: Tuhada primary EC2 instance down ho janda Aah. Ki standard DNS automatically traffic dooje instance te bhej dega?

Nahi. Standard DNS nu server di health da nahi pta hunda. Par Route 53 'Health Checks' aur 'Failover Routing' use karke automatically healthy server te traffic bhej sakda Aah.

What is DNS?

Domain Name System - Internet di phonebook jo naama (domains) nu IP addresses (numbers) vich translate kardi Aah.

What is Amazon Route 53?

AWS di managed, highly available DNS service jo domain registration, smart DNS routing, aur health checks provide kardi Aah.

Route 53 aur DNS de farak nu 'Phonebook' di analogy naal kivein explain karange?

DNS ek aam paper 'Phonebook' varga Aah (Concept). Route 53 ek 'Smart Exchange' Aah jo na sirf number dasda Aah, balki check karda Aah ki agla server available Aah ya nahi, aur us according call (traffic) route karda Aah.

"DNS ek protocol ya concept Aah…"

Asali Matlab: DNS internet da standard rule Aah IP translation layi, koi specific company di property nahi.

"…aur Route 53 AWS di Managed Service Aah."

Asali Matlab: Route 53 AWS da banaya ek tool Aah jo DNS te based Aah, aur isde servers di maintenance di tension AWS lenda Aah.

"Route 53 Health Checks perform karda Aah."

Asali Matlab: Route 53 continuously servers nu monitor karda Aah aur sirf zinda (healthy) servers nu hi DNS query da IP response dinda Aah.

Domain Name System (DNS)

Naming system jo www.example.com nu machine-readable IP 192.0.2.1 vich convert karda Aah.

Route 53

AWS di Managed DNS Web Service. Isda naam '53' Port number ton aaya Aah jis te DNS protocol operate karda Aah.

Health Checks

Route 53 da powerful feature jo endpoints (servers) di health continuously verify karda Aah taaki traffic dead server te na jave.

Tussi apni website da nava IP update kitta, par purane customers nu aje vi purani website dikh rahi Aah. Kyu?

Kyunki unhna de ISP de DNS Resolver ne purana IP "Cache" kitta hoya Aah. Jadon tak purane record da TTL (Time To Live) expire nahi hunda, ohna nu nava IP nahi milega.

Ki tussi kisi Root Domain (jivein example.com) nu CNAME de through kisi dooje domain naal map kar sakde ho?

Nahi. DNS rules de mutabik, Root domain te CNAME nahi lag sakda. (Isee problem nu solve karan layi AWS Alias records use karda Aah).

What is a Recursive Resolver?

ISP da oh DNS server jo user de behalf te Root, TLD aur Authoritative servers kol ja ke asali IP labh ke liyanda Aah.

What is an Authoritative Name Server?

DNS chain da aakhri server jis kol website de asali DNS records (A, CNAME) di zone file hundi Aah.

DNS Resolution process nu 'Investigation' di analogy naal kivein explain karange?

Resolver ek 'Detective' Aah, jo pehlan 'Global HQ' (Root) kol janda Aah, fir 'State Dept' (TLD) kol, aur aakhri ch 'Local Station' (Authoritative) kol ja ke exact IP address labhda Aah.

"Root servers internet di top hierarchy ne"

Asali Matlab: Jadon cache khali hunda Aah, taan DNS di sabton pehli query hamesha duniya de 13 Root servers vicho kisi ek nu hit kardi Aah.

"TTL value nu ghatt karna"

Asali Matlab: Migration de time cache nu jaldi clear karvaun layi TTL nu 300s ya 60s te set karna, taaki downtime ghatt hove.

Ki duniya vich asaliyat ch sirf 13 hi physical Root Servers ne?

Nahi. 13 sirf "Logical IP Addresses" ne. Anycast routing di wajah naal inha 13 IPs de piche duniya bhar ch 1,700 ton zyada physical servers kaam karde ne.

Kyu internet de architects ne specifically "13" Root servers hi banaye? 14 kyu nahi?

Kyunki shuruati DNS queries UDP (User Datagram Protocol) use kardiyan si, jisdi 512-byte di strict size limit si. Us 512 bytes vich maximum 13 IP addresses hi fit aa sakde si.

What is the UDP 512-byte Limit?

Networking di oh purani history jisne DNS Root Servers di ginti nu 13 IP addresses tak limit kar ditta si.

What is Anycast in Root Servers?

Oh technology jo inha 13 logical IP addresses nu hazaran physical servers te distribute kardi Aah taaki internet kade down na hove.

13 Root Servers nu 'Commanders' di analogy naal kivein explain karange?

Eh 13 Supreme Commanders ne. Oh khud border te nahi lad de, ohna ne duniya bhar ch apne 'clones' (servers) rakhe ne jo same name aur badge (IP address) use karde ne.

"Root server resolver nu TLD Name Server da IP dinda Aah."

Asali Matlab: Root server kade vi final IP nahi dinda, oh sirf next department (.com, .in) da address dinda Aah.

"Resolver final query authoritative server nu karda Aah."

Asali Matlab: Authoritative server (jivein Route 53) us chain da aakhri stop Aah jis kol asali Zone File (A record) hunda Aah.

Recursive Resolver

Tuhada ISP da assistant jo tuhade behalf te IP address labhan di saari investigation karda Aah.

TLD (Top-Level Domain) Server

Oh middle-man servers jo specific extensions jivein .com, .org, ya .in nu handle karde ne.

ICANN

Oh international sanstha (organization) jo inha Root Servers de rules aur internet namespaces nu manage kardi Aah.

AWS Route 53 default roop ch ek Hosted Zone layi kinne Name Servers (NS) dinda Aah?

4 Managed Name Servers.

Scenario: Tuhade Hosted Zone de 4 Name Servers vicho ek (.com wala) down ho janda Aah. Ki tuhadi website offline ho jayegi?

Nahi. Baaki bache 3 Name Servers (.net, .org, etc.) traffic nu route karna continue rakhange. Eh High Availability ensure karda Aah.

Ki Hosted Zone create karan naal AWS automatically TLD registry kol NS records add kar dinda Aah?

Nahi. Hosted Zone creation sirf AWS de andar 4 NS allocate karda Aah. Tuhanoo eh 4 NS records manually apne Domain Registrar (jivein GoDaddy ya Route 53 domains) ch ja ke update karne painde ne.

What is a Hosted Zone in Route 53?

Ek container jis vich ek specific domain name (aur usde subdomains) de DNS records (jivein A, CNAME, MX) store hunde ne.

What are NS Records?

Name Server records. Eh oh records ne jo internet nu dasde ne ki is domain di DNS queries nu solve karan layi kis server kol jaana Aah.

4 Name Servers nu 'Building de Pillars' di analogy naal kivein explain karange?

Hosted Zone ek internet te plot Aah, aur AWS isnu stable rakhan layi 4 alag-alag Pillars (Name Servers) dinda Aah. Agar ek pillar gir vi jave, taan baaki 3 building (website DNS) nu handle kar lende ne.

"default roop ch us zone nu"

Asali Matlab: Tuhanoo NS server manually choose ya build nahi karne painde, Route 53 zone create hon te automatically eh kaam karda Aah.

"globally distributed 4 managed name servers"

Asali Matlab: Eh chaaro servers alag-alag TLDs (.com, .org, .net, .co.uk) te base hunde ne taaki kisi global outage ton bache rehan aur inki maintenance AWS karda Aah.

Hosted Zone

Route 53 vich DNS records da collection/container (Public ya Private).

NS (Name Server) Record

Oh record jo DNS queries nu authoritative server wal point karda Aah.

Managed Servers

Oh infrastructure jisdi security, uptime aur maintenance AWS de control ch hundi Aah.

Hosted Zone create karan ton baad ki AWS khud TLD registry kol ja ke NS update karda Aah?

Nahi. AWS sirf apne andar ek container (plot) bananda Aah. TLD ya Registrar kol ja ke NS records update karna tuhadi (customer di) zimmewari hundi Aah.

Scenario: Tussi AWS ch Hosted Zone banaya par domain GoDaddy ton leya Aah. Tussi NS records update nahi kite. Ki website chalegi?

Nahi chalegi. Internet GoDaddy kol jaake website da address puchega, aur GoDaddy kol AWS de 4 NS pillars da address (GPS coordinates) nahi hovega, isliye website offline rahegi.

CNAME aur A Record vich asali farak ki Aah?

A Record hamesha Domain nu IP Address (Numbers) naal map karda Aah. CNAME hamesha Domain nu kisi dooje Domain (Naam) naal map karda Aah.

What is a TLD (Top-Level Domain)?

Internet de alag-alag 'States' ya extensions (jivein .com, .org, .in) jinna nu specific global organizations manage kardiyan ne.

What is a Domain Registrar?

Oh 'Dukaan' (jivein GoDaddy, Namecheap, Route 53 Domains) jitho tussi apna website da naam (Domain) paise de ke khareed de ho.

What is PIR?

Public Interest Registry. Eh oh global sanstha (Sarkari Daftar) Aah jisde kol '.org' TLD da poora control hunda Aah.

What is a TLD (Top-Level Domain)?

Internet de alag-alag 'States' ya extensions (jivein .com, .org, .in) jinna nu specific global organizations manage kardiyan ne.

What is a Domain Registrar?

Oh 'Dukaan' (jivein GoDaddy, Namecheap, Route 53 Domains) jitho tussi apna website da naam (Domain) paise de ke khareed de ho.

What is PIR?

Public Interest Registry. Eh oh global sanstha (Sarkari Daftar) Aah jisde kol '.org' TLD da poora control hunda Aah.

Hosted Zone, NS Records, aur Registrar nu 'Plot aur Registry' di analogy naal kivein explain karange?

Hosted Zone tuhada AWS te nawa 'Plot' Aah. NS Records us plot de 'GPS Coordinates' ne. Registrar oh 'Dukaan' Aah jisne naam vecheya Aah, aur tuhanu us dukaan te ja ke apne plot de GPS coordinates khud update karne painde ne.

A Record aur MX Record vich 'Traffic Police' di analogy kivein lagdi Aah?

Hosted Zone ek Traffic Police Aah. A Record wale rules website de traffic nu Web Server wale kamre ch bhej de ne, aur MX Record wale rules Email di traffic nu Mail Server (Google/Outlook) wale kamre ch bhej de ne.

"TLD registry (jivein .org layi PIR)"

Asali Matlab: Har TLD extension (.com, .org) nu handle karan layi internet te ek supreme authority hundi Aah, jivein .org nu PIR sambhaldi Aah.

"(Registrar kol ja ke oh NS records update karna tuhadi zimmewari hundi Aah)"

Asali Matlab: Kyunki TLD registry seedha public naal gal nahi kardi, isliye tuhanu apne Registrar (GoDaddy etc.) account ch login karke "Custom Nameservers" vich AWS de 4 NS links paste karne painde ne taaki domain AWS naal point ho jave.

"de saare DNS rules save honge"

Asali Matlab: Hosted Zone sirf ek khali plot nahi Aah, isde andar routing de rules (Zone File) likhe jande ne ki kis type di request nu kithe bhejna Aah.

A Record (Address Record)

Oh rule jo domain name (example.com) nu direct IPv4 address (192.168.1.1) naal map karda Aah.

CNAME Record (Canonical Name)

Oh rule jo ek naam nu dooje naam (nickname) naal map karda Aah (jivein www.example.com nu example.com te forward karna).

MX Record (Mail Exchange)

Oh rule jo specifically Email traffic nu handle karda Aah aur usnu sahi Mail Server val route karda Aah.

DNS Pointing

Apne khareede hoye Domain de settings vich ja ke AWS de NS records update karan di process.

Amazon-provided DNS Server

VPC da in-built resolver jo external aur internal DNS queries process karda Aah.

DNS Resolution Fail

Oh network error jo udon aanda Aah jadon Internal DNS Engine band hove ya galat configured hove.

"Internal DNS Engine on hove"

Asali Matlab: VPC level te 'enableDnsSupport' attribute da enabled (TRUE) hona taaki VPC da internal resolver activate ho jave.

'Internal DNS Engine' nu 'Telephone Exchange' di analogy naal kivein explain karange?

Jivein ek society de andar flats nu aapas ch connect karan layi basement ch ek private PBX (Telephone Exchange) hunda Aah, usivein VPC de andar instances nu DNS naal connect karan layi AWS da eh internal engine hunda Aah.

What is the Amazon-provided DNS Server?

Eh VPC da internal DNS engine Aah jo hamesha VPC CIDR de +2 IP address te maujood hunda Aah.

Amazon RDS

Managed backend database service (jivein MySQL, PostgreSQL) jisnu tussi Private Hosted Zone ch hide karde ho.

VPC Resolver

Tuhade subnet da internal DNS server jo hamesha VPC de starting IP vich +2 add karke milda Aah.

enableDnsSupport

VPC level switch jo determine karda Aah ki DNS queries VPC de andar resolve hongiyan ya nahi.

enableDnsHostnames

VPC level switch jo allow karda Aah ki AWS apne resources nu internally DNS names (strings) assign kare.

"Bahar ton (Internet ton) eh query aayegi taan Route 53 sidha reject kar dega"

Asali Matlab: Private Hosted Zone AWS de internal network ton aayi request hi accept karda Aah. Public internet di queries nu oh NXDOMAIN (nahi mila) keh dinda Aah.

"VPC Network Range + 2 IP address"

Asali Matlab: Har VPC vich ek hardcoded rule Aah ki IP address number 2 hamesha DNS queries solve karan wale hidden internal server (resolver) kol hovega.

'enableDnsSupport' aur 'enableDnsHostnames' nu 'Intercom' di analogy naal kivein explain karange?

'enableDnsSupport' intercom di power wire Aah (DNS engine on karda Aah). 'enableDnsHostnames' intercom di directory list Aah (Naam assign karda Aah). Private Zone (secret contacts) dekhan layi dono da on hona zaroori Aah.

What is Amazon RDS?

Relational Database Service - AWS da managed database solution jithe AWS maintenance handle karda Aah.

What is the "VPC + 2" IP address?

Eh Amazon-provided internal DNS server (Route 53 Resolver) da exact address hunda Aah har VPC de andar.

Agar tuhade VPC da base CIDR block 172.16.0.0/16 Aah, taan us VPC da default Amazon DNS Resolver kis IP address te hovaga?

172.16.0.2 (VPC Network Range + 2 IP address). AWS hamesha is IP nu DNS resolver layi reserve rakhda Aah.

Scenario: Tussi Private Hosted Zone banaya aur VPC naal link vi kita. Tuhada EC2 database da naam ping nahi kar paa reha. Tussi check kita taan 'enableDnsSupport' TRUE si, par 'enableDnsHostnames' FALSE si. Ki issue Aah?

Private Hosted Zone nu kamm karan layi eh dono (enableDnsSupport aur enableDnsHostnames) lazmi TRUE hone chaahide ne. Ek de vi FALSE hon naal internal routing fail ho jandi Aah.

RDS Database ki Aah aur tussi isnu kyu use karoge?

Eh Amazon di managed Relational Database service Aah. EC2 te khud database install karan di mehnat (backups, updates, scaling) ton bachan layi AWS di eh ready-made service use kiti jandi Aah.

Private Hosted Zone

Internal domain resolution layi isolated DNS container.

Public Hosted Zone

Internet-facing domain resolution layi globally available DNS container.

enableDnsSupport

VPC setting jo Amazon-provided DNS server nu enable kardi Aah (Private zones layi required).

enableDnsHostnames

VPC setting jo instances nu public/private DNS hostnames assign kardi Aah (Private zones layi required).

"public internet toh hide krna chaaunde ho"

Asali Matlab: Internal architecture aur backend IP structures nu external hackers ton bacha ke rakhna (Security best practice).

"explicitly ek ya us toh Vaddhe VPCs naal link Hunde Aah"

Asali Matlab: Private Hosted Zones di visibility strictly ohna VPCs tak limit hundi Aah jinna nu manual ya automated tarike naal attach kita gaya hove.

Private Hosted Zone nu 'Intercom' di analogy naal kivein explain karange?

Public zone ek public phonebook Aah jisko koi vi dekh sakda Aah. Private zone ek office da internal Intercom Aah, jisde numbers sirf office (VPC) de andar baithe employees hi dial kar sakde ne.

What is a Private Hosted Zone?

Route 53 da oh container jo internal AWS networks (VPCs) layi private domain names nu IP addresses vich resolve karda Aah.

VPC Link (in context of Route 53)

Oh strict association/connection jo ek Private Hosted Zone nu specific VPCs tak limit karda Aah.

Scenario: Tussi ek Private Hosted Zone banaya Aah par tuhade VPC de EC2 instances usnu resolve nahi kar pa rahe. Route 53 configuration theek Aah. Farak kithe ho sakda Aah?

VPC di settings vich 'enableDnsHostnames' aur 'enableDnsSupport' options 'True' (enabled) nahi hongi. Private Hosted Zone chalaunda layi eh dono true hone chaahide ne.

Ki tussi ek hi Private Hosted Zone nu do alag-alag AWS Regions de VPCs naal link kar sakde ho?

Haan, tussi ek Private Hosted Zone nu multiple VPCs naal link kar sakde ho, chahe oh alag-alag Regions vich hi kyu na hon.

Agar koi internet ton tuhade Private Hosted Zone wale domain nu ping kare taan ki hovaga?

Query fail ho jayegi (NXDOMAIN error). Route 53 private records nu public internet te resolve nahi karda.

"domain di saari DNS information"

Asali Matlab: Oh 6-7 type de routing rules (A, Alias, MX, TXT) jo traffic nu sahi server, load balancer, ya mailbox tak pahunchande ne.

"Alias records Route 53 da custom feature ne"

Asali Matlab: Eh standard DNS da part nahi ne, eh AWS da apna logic Aah jo dynamic resources (jivein ALB) nu map karda Aah oh vi bina DNS query charges de.

Alias Record

AWS specific routing rule jo AWS resources (ALB, S3, CloudFront) nu map karan layi use hunda Aah, khaaskar root domain te.

Zone Apex

Tuhada asali nanga domain name, bina kisi 'www' ya subdomain de (jivein: example.com).

TXT Record

Domain verification aur email security (SPF/DKIM) layi text-based information store karan wala record.

Hosted Zone de andar MX aur A records nu 'Ghar' di analogy naal kivein samjhavange?

A Record ghar da 'Main Darwaza' Aah jithe web traffic aundi Aah. MX Record ghar da 'Letterbox' Aah jithe sirf chithiyan (Emails) aundiyan ne, taaki dono traffic mix na hon.

What is an SOA Record?

Start of Authority. Eh us zone da master record hunda Aah jisvich domain admin di details aur global caching timers (TTL) set hunde ne.

What is a CNAME Record?

Oh record jo ek domain (subdomain) nu kisi dooje domain name val point karda Aah (IP address wal nahi).

Tussi Route 53 vich ek nawa Hosted Zone create kita. Tuhade bina koi record add kite, us zone vich pehlan ton kede do records maujood honge?

NS (Name Server) aur SOA (Start of Authority) records. AWS eh dono by default bananda Aah.

Scenario: Tussi apne main root domain (example.com) nu apne AWS Application Load Balancer (ALB) naal map karna Aah. Tussi CNAME use karoge ya Alias record?

Alias Record. CNAME kade vi root domain (Zone apex) te nahi lag sakda, aur Alias record AWS resources layi free aur zyada fast hunda Aah.

A Record Update Jadon server da asali IPv4 address change hunda Aah taan tuhanu Route 53 ch ja ke isnu edit karna painda Aah.

TTL (Time-To-Live) Expiration Oh moment jadon DNS cache khatam hunda Aah aur client (laptop) nawa DNS record mangda Aah.

"baaki 10 apne aap naye raste te chale jange" Asali Matlab: CNAME use karan naal oh 10 records main domain de A record nu track karde ne. A record da IP badalde hi

CNAME wale baaki 10 vi automatic naye IP te route ho jande ne.

"kinni der cache karegi" Asali Matlab: TTL (seconds vich) oh countdown timer Aah jis ton baad internet service providers di memory ch purana IP address automatically delete ho janda Aah.