// dns
translate domain names to ip address
===========
// domain registrar.
domain di register via interNIC == service provided by ICANN / internet corp for assigned names and number
- klo udah diregister nanti datanya masuk di WhoIS database
contoh domain registrar:
- hostgator
- godaddy
- domain.com
- aws
- namecheap
- bs bayar service tambahan biar dnsnya ke private
============
// top leveldomain
- word terakhir di domain name
contoh : .com .ac .academy .aaa .abb
bs dicek di availability database:
www.iana.org/domains/root/db
^ aws cuma top level domain .aws
===========
// second level domain
- 2nd word setelah domain name
contoh:
toro.co.id // co = 2nd level domain
===========
// Start of authority
tiap domain hrs punya SOA record yg bs provide informasi tentang domain.
contoh:
- seberapa sering diupdate
- admin email
1 zone file cuma bs contain 1 SOA Record.
format:
[authority-domain] ---- [domain-of-zone-admin] ----- [ zone-SN ] ----
[refresh-time] ---- [ retry-time] ---- [ expire-time ] ----
[negative caching TTL]
contoh:
ns.example.com. hostmaster.example.com. 1
7200 900 1209600 86400
aws example:
ns-415.awsdnns-51.com. awsdns-hostmaster.amazon.com. 1
7200 900 1209600 86400
===========
// A Record
A record : buat convert nama domain directly ke ip address.
{
"ResourceRecordSets":[
{
"TTL":300,
"Type": "A",
"Name": "testing-domain.com",
"ResourceRecords" : [
{ "Value": "202.169.228.1" }
]
}
]
}
===========
// cname
- resolve one domain name to another rather than ip address
- klo dipasang cname, kita bs ubah A record tp pointing cnamenya tetep sama.
{
"ResourceRecordSets":[
{
"TTL":300,
"Type": "CNAME",
"Name": "testing-domain.com",
"ResourceRecords" : [
{ "Value": "wwww.testing-domain.com" }
]
}
]
}
=========
// NS
digunakan oleh top level domain buat direct traffic ke dns server yg merupakan
authoritative DNS record.
- bs bikin multiple name server buat redundancy
- klo kita bikin dns record pake route53, NS Record buat domain kita bakal pointing ke AWS Servers.
{
"Type": "NS",
"ResourceRecordSets":[
{
"Name": "testing-domain.com",
"TTL":172800,
"ResourceRecords" : [
{ "Value": "ns-245.awsdns-30.com." },
{ "Value": "ns-523.awsdns-30.net." },
{ "Value": "ns-1586.awsdns-30.co.uk." },
{ "Value": "ns-1373.awsdns-43.org." },
]
}
]
}
========
// TTL
waktu yg diperbolehkah oleh dns record buat di cached di server / user local machine
semakin pendek nilai ttl, semakin cepet changes dns record propagate accross internet
=========
// route 53
- high available and scalable cloud DNS.
- register and manage domain
- create dns routing rules / failover
- lebih ke sinergy ddengan aws services
- bs register and manage domain
- create various record set on domain
- implement complex traffic flows
- continous monitor record via health checks
- resolve vpc diluar AWS
=========
// route 53 record sets
- buat pointing naked domain dan subdomain via domain record
A record => pointing ke spesifik ip
===========
// alias record aws
- extends dns functionality
- route traffic to specific AWS Resources
- alias record bs detect change ip addr dan keep state ip dari endpoint pointed to correct resources
- dipake kl mau ngeroutingin traffic kedalem AWS Services
==========
// routing policies
ada 7:
1 simple routing
- default. multiple address = result in random selection
2 weighted routing
- routing berdasarkan weight buat split traffic
- misal : 80% traffic to server 1 , 20% to server 2
3 latency based routing
- routing traffic ke region dengan lowest latency
- ga peduli geographicnya adda dimana, yg penting ms terkecil yg dipilih
4 failover routing
- route traffic klo primary endpoint = unhealthy => lempar ke secondary endpoint
- buat bikin active - passive situation
- auto monitor health check from primary
5 geolocation routing
- route traffic based on location of users
6 geo-proximity routing
- route traffic berdasarkan lokasi resource and optionally shift traffic from resource in one location to resources in anothers
7 multi-value answer routing
- respond dns queries up to 8 healthy record ( random selection )
- mirip kyk simple routing policies tp ditambahin ++ health check
=========
// route 53 - traffic flow
- visual editor. lets u create multiple routing config for ur resource using existing routing types
- support versioning for rollback
- 50$ per policy record per month
=========
// health check
- tiap 30s by default. bs dicustom tiap 10s.
- kita bs pasang cloudwatch alarm buat alert status unhealthy
- health check bs di chaining. bs monitor other health check to create a chain of reactions. up to 50 single aws account
=======
// route 53 resolver ( .2 resolver )
- regional service yg bs route dns queries between vpc and network
- dns resolution buat hybrid environtment ( on prem dan cloud )
ada 3
- inbound and outbound
- inbound only
- outbound only
=======
No comments:
Post a Comment