I believe there might be a confusion but we can have a thought on this: DNS resolution, which is the process of translating domain names into IP addresses, typically occurs before the request reaches the web server, but it doesn't happen exclusively on the client side. Here's a simplified overview of the typical DNS resolution process: 1. The client, such as a web browser, initiates a request to access a website by entering a domain name (e.g., example.com) into the address bar. 2. The client's operating system checks its local DNS cache to see if it already has the corresponding IP address for the domain. If the IP address is found, the DNS resolution process ends, and the client proceeds to make a connection to the web server. 3. If the IP address is not found in the local DNS cache, the client's operating system sends a DNS query to a configured DNS resolver (usually provided by the ISP or a public DNS service like Google DNS or Cloudflare DNS). This query contains the domain name that needs to be resolved. 4. The DNS resolver receives the query and checks its own cache for the requested domain's IP address. If found, it responds to the client with the IP address. 5. If the IP address is not cached by the resolver, it performs the necessary steps to resolve the domain. This may involve querying other DNS servers in the DNS hierarchy until a DNS server is found that can provide the IP address. Eventually, the resolver obtains the IP address for the requested domain. 6. The DNS resolver sends the IP address back to the client. 7. With the IP address in hand, the client establishes a connection to the web server using the obtained IP address. 8. The web server receives the client's request and processes it, eventually sending back the requested web page or resource. In summary, DNS resolution typically occurs on the client side or the client's operating system, but it involves interactions with DNS resolvers and possibly other DNS servers in the DNS hierarchy. The web server itself is not directly responsible for DNS resolution but receives the client's request after the resolution process has taken place.
@@Pythoholic can you please confirm by reviewing the latest doc because it says as per the updated regaulations we'll not save your recent or previous card information you have to pay manually.. If this is true that I think this is exactly I want but if it is not then please guide through steps to disable this functionality. Thanks
Yes I check mine. it is mentioned that it will not save. If it got deducted then it's better to reach out support. If not then I would suggest removing the payment details for now.. and adding it when u want to pay the bill
Explanation in the video matching the title. It's ultimate as well as detailed! Delivering the best as usual @pythoholic!
Thanks a lot Sachin 🙏
Wow! Very good explanation! I really enjoyed learning...thank you!
Bro please continue doing the videos.
Your explanation is crystal clear
Thanks bro
I can imagine how much effort you put on those presentations! Well done!!
Glad you like them!
Sir, you are taking lot of efforts thank you so much well done sir
U r the best. Dont stop making edu videos.
Thanks 🙏
Shouldn’t the diagram at 2:18 & 4:02 have ISP in place of 'web server',
Something like:
User -> Req ISP DNS
-> WebServer
Awesomely Explained.
🙏
Really valuable content bro.... please do more videos bro....🙏🙏🙏🙏
Thanks deepu
Splendid work !!!
Please make project based tutorial series using AWS CDK and boto3.
Thanks Yash for sure
Explanation in Cool way ❤❤
🙏
Thanks for uploading all this viedo it's really helpful for me .. could you please make a video for ECS service and Glue service
Thanks I have a video on eks I will upload on ecs and glue as well
Can you please make a masterclass for EC2 like you did a 6 hour vid for vpc
We can do that. Thanks for the suggestion
19:00 bookmark
DNS resolution doesn't happen at Web Server but at the client side and only then does it reach the Web Server. You need to correct @2:34.
I believe there might be a confusion but we can have a thought on this: DNS resolution, which is the process of translating domain names into IP addresses, typically occurs before the request reaches the web server, but it doesn't happen exclusively on the client side.
Here's a simplified overview of the typical DNS resolution process:
1. The client, such as a web browser, initiates a request to access a website by entering a domain name (e.g., example.com) into the address bar.
2. The client's operating system checks its local DNS cache to see if it already has the corresponding IP address for the domain. If the IP address is found, the DNS resolution process ends, and the client proceeds to make a connection to the web server.
3. If the IP address is not found in the local DNS cache, the client's operating system sends a DNS query to a configured DNS resolver (usually provided by the ISP or a public DNS service like Google DNS or Cloudflare DNS). This query contains the domain name that needs to be resolved.
4. The DNS resolver receives the query and checks its own cache for the requested domain's IP address. If found, it responds to the client with the IP address.
5. If the IP address is not cached by the resolver, it performs the necessary steps to resolve the domain. This may involve querying other DNS servers in the DNS hierarchy until a DNS server is found that can provide the IP address. Eventually, the resolver obtains the IP address for the requested domain.
6. The DNS resolver sends the IP address back to the client.
7. With the IP address in hand, the client establishes a connection to the web server using the obtained IP address.
8. The web server receives the client's request and processes it, eventually sending back the requested web page or resource.
In summary, DNS resolution typically occurs on the client side or the client's operating system, but it involves interactions with DNS resolvers and possibly other DNS servers in the DNS hierarchy. The web server itself is not directly responsible for DNS resolution but receives the client's request after the resolution process has taken place.
can you make us a tutorial video please ?
Please continue doing more devops video
Thanks Manu .. sure will do that
What is the tool name you used to create the slide?
Just ppt :)
Could someone please verify whether AWS charges me and automatically debits the funds from my account?
It can do it if you have checked auto payment enabled. You can raise a support ticket if you feel it's not correct.
@@Pythoholic can you please confirm by reviewing the latest doc because it says as per the updated regaulations we'll not save your recent or previous card information you have to pay manually.. If this is true that I think this is exactly I want but if it is not then please guide through steps to disable this functionality. Thanks
Yes I check mine. it is mentioned that it will not save. If it got deducted then it's better to reach out support. If not then I would suggest removing the payment details for now.. and adding it when u want to pay the bill
@@Pythoholic yes that is the confirmation I need.. Thanks
14:43 that diagram is incorrect.
Thanks will check and correct it
U are a man or james bond ?
i will go to deepika's house at the first place............
🤣🤣🤣🤣