<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Junior Dev]]></title><description><![CDATA[Junior Dev]]></description><link>https://indrajeetdev.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Tue, 01 Sep 2026 01:09:43 GMT</lastBuildDate><atom:link href="https://indrajeetdev.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Git for Beginners: Basics and Essential Commands]]></title><description><![CDATA[What is Git
Git is a tool used by developers to manage code. It help save changes in files over time. Git remember what change you did and when you did. If something break you can go back to old version. Git work on your computer and not only on inte...]]></description><link>https://indrajeetdev.hashnode.dev/git-for-beginners-basics-and-essential-commands</link><guid isPermaLink="true">https://indrajeetdev.hashnode.dev/git-for-beginners-basics-and-essential-commands</guid><dc:creator><![CDATA[Indrajeet Jha]]></dc:creator><pubDate>Sat, 31 Jan 2026 17:02:40 GMT</pubDate><content:encoded><![CDATA[<p>What is Git</p>
<p>Git is a tool used by developers to manage code. It help save changes in files over time. Git remember what change you did and when you did. If something break you can go back to old version. Git work on your computer and not only on internet.</p>
<p>Developer → Git → Code History</p>
<p>Why Git is Used :-</p>
<p>Git is used because coding without backup is risky. When many developers work together Git help avoid confusion. Git also help track mistakes and improve teamwork. It save time and keep code safe.</p>
<p>Code Changes → Git → Safe Storage</p>
<p>Git Basics and Core Terminologies:-</p>
<p>Repository means a folder where Git track files. Commit means saving changes with message. Branch means copy of code to work safely. Head point to current commit you are working on. These are main words used in Git and beginner should know them.</p>
<p>Repo → Branch → Commit → Head</p>
<p>What is a Repository</p>
<p>Repository is main folder of project. Git store all history inside repository. It can be local on computer or remote on GitHub. Every Git project start with repository.</p>
<p>Project Folder → Git Repository</p>
<p>What is a Commit:-</p>
<p>Commit means saving your work. When you commit Git take snapshot of files. Commit have message to explain what you changed. Many commits make project history.</p>
<p>Files → Commit → History</p>
<p>What is a Branch:-</p>
<p>Branch allow you to work without breaking main code. You can create new branch try new feature then merge later. Branch help experiment safely.</p>
<p>Main Branch → New Branch → Changes</p>
<p>Common Git Commands:-</p>
<p>Git commands are used in terminal. git init create new repository. git status show file state. git add move files to staging. git commit save changes. git log show commit history. These commands are enough to start Git.</p>
<p>git init → git status → git add → git commit → git log</p>
<p>Git Working Directory Staging and Repository:-</p>
<p>Working directory is where you edit files. Staging area is middle place before commit. Repository store commits permanently. Git move files step by step.</p>
<p>Working Directory → Staging Area → Repository</p>
<p>Basic Developer Workflow Using Git:-</p>
<p>First developer create repository. Then write code. Then add files. Then commit changes. This process repeat many times. This is daily life of developer.</p>
<p>Code → Add → Commit → Repeat</p>
<p>Local Repository Structure:-</p>
<p>Local repository live on your computer. It store commits branches and head. Git manage everything inside hidden folder. Developer only see files but Git see history.</p>
<p>Local Repo → Commits → Branches</p>
<p>Commit History Flow:-</p>
<p>Commit history show timeline of project. Each commit link to previous one. This make chain of changes. Git log show this flow.</p>
<p>Commit 1 → Commit 2 → Commit 3</p>
<p>Why Git is Important for Beginners</p>
<p>Git is must skill for developer. Every company use Git. Learning Git early make coding journey smooth. Even solo developer need Git.</p>
<p>Beginner → Git → Professional Growth</p>
]]></content:encoded></item><item><title><![CDATA[How DNS Resolution Works]]></title><description><![CDATA[DNS and dig Command :-
What is DNS and why name resolution exists
DNS means Domain Name System. DNS is like phonebook of internet. Human remember name not number but computer only understand number. So DNS help change name like google.com into IP add...]]></description><link>https://indrajeetdev.hashnode.dev/how-dns-resolution-works</link><guid isPermaLink="true">https://indrajeetdev.hashnode.dev/how-dns-resolution-works</guid><dc:creator><![CDATA[Indrajeet Jha]]></dc:creator><pubDate>Wed, 28 Jan 2026 13:21:13 GMT</pubDate><content:encoded><![CDATA[<p>DNS and dig Command :-</p>
<p>What is DNS and why name resolution exists</p>
<p>DNS means Domain Name System. DNS is like phonebook of internet. Human remember name not number but computer only understand number. So DNS help change name like google.com into IP address. Without DNS we have to remember long numbers for every website. Name resolution exist to make internet easy for humans.</p>
<p>Browser → DNS → IP Address</p>
<p>What is the dig command and when it is used:-</p>
<p>dig is a command used in terminal to check DNS details. It help programmers and network people to see how DNS is working. dig does not open website it only ask DNS questions. When website not opening dig is used to find problem.</p>
<p>Terminal → dig → DNS Server':-</p>
<p>Understanding dig . NS and root name servers</p>
<p>When we run dig dot NS it ask about root name servers. Root servers are top level of DNS. They do not know IP of website but they know where TLD servers are. Root servers help start the DNS journey. They guide request to next level.</p>
<p>dig . NS</p>
<p>Client → Root Server → TLD Info</p>
<p>Understanding dig com NS and TLD name servers:-</p>
<p>When we use dig com NS it ask TLD servers for dot com. TLD servers manage domains like google.com facebook.com etc. They do not store website IP but they know authoritative servers. TLD is middle layer of DNS.</p>
<p>dig com NS</p>
<p>Root → TLD Server → Authoritative Direction</p>
<p>Understanding dig google.com NS and authoritative name servers:-</p>
<p>When we run dig google.com NS it show authoritative name servers of google. Authoritative servers are final boss of DNS. They store real DNS records like A record MX record. They are responsible for domain data.</p>
<p>dig google.com NS</p>
<p>TLD → Authoritative Server → Real Records</p>
<p>Understanding dig google.com and full DNS resolution flow:-</p>
<p>When we type dig google.com it show final answer with IP address. Behind the scene recursive resolver talk to root then TLD then authoritative server. User only see result but many steps happen silently. Browser also follow same process.</p>
<p>Client → Recursive Resolver → Root → TLD → Authoritative → IP</p>
<p>What NS records represent and why they matter:-</p>
<p>NS record tell who control a domain DNS. It point to authoritative name servers. Without NS record domain will not work. NS record is like manager of domain who know all records.</p>
<p>Domain → NS Record → DNS Control</p>
<p>How recursive resolver works behind the scene:-</p>
<p>Recursive resolver is usually run by ISP or public DNS. It do all DNS searching work for user. It ask root then TLD then authoritative server. User computer do not do heavy work. This make internet fast and smooth.</p>
<p>User → Recursive Resolver → Internet DNS</p>
<p>Connecting dig output to browser request</p>
<p>Browser also do same DNS lookup but hide details. dig show raw data. When browser open google.com it use recursive resolver just like dig. So learning dig help understand browser networking.</p>
<p>Browser → DNS Lookup → Server → Website</p>
<p>DNS hierarchy in simple words:-</p>
<p>DNS is layered system. Each layer know different thing. Root know TLD. TLD know authoritative. Authoritative know IP. This design keep system scalable.</p>
<p>Root → TLD → Authoritative</p>
<p>Step by step DNS resolution for google.com:-</p>
<p>First browser ask resolver. Resolver ask root. Root send TLD info. TLD send authoritative info. Authoritative send IP. Browser connect to server.</p>
<p>Browser → Resolver → Root → TLD → Auth → IP</p>
<p>Where dig fits in system design:-</p>
<p>dig is tool to understand system design of DNS. It show how distributed system work. Every backend and devops learner should know dig to debug DNS issues.</p>
<p>Developer → dig → DNS System</p>
]]></content:encoded></item><item><title><![CDATA[DNS Record Types Explained]]></title><description><![CDATA[How browser know where a website live
DNS record explained in very easy words
When I type a website name like google.com in browser and press enter, the website open very fast I never write any IP address Still the website comes So one question come ...]]></description><link>https://indrajeetdev.hashnode.dev/dns-record-types-explained</link><guid isPermaLink="true">https://indrajeetdev.hashnode.dev/dns-record-types-explained</guid><dc:creator><![CDATA[Indrajeet Jha]]></dc:creator><pubDate>Mon, 26 Jan 2026 12:32:00 GMT</pubDate><content:encoded><![CDATA[<h1 id="heading-how-browser-know-where-a-website-live">How browser know where a website live</h1>
<h3 id="heading-dns-record-explained-in-very-easy-words">DNS record explained in very easy words</h3>
<p>When I type a website name like <a target="_blank" href="http://google.com"><code>google.com</code></a> in browser and press enter, the website open very fast I never write any IP address Still the website comes So one question come in mind that how does the browser knows where the Website live and the answer is known as DNS</p>
<hr />
<h2 id="heading-what-is-dns">What is DNS</h2>
<p>Its fullform is Domain Name Stystem DNS is like phonebook of internet People like to remember names like eg : google.com but computer only understand numbers like: 142.250.78.63. DNS change website name into number so computer can find the website. Like in phone we save name and phone save number inside, DNS also save website name with number.</p>
<p>Without DNS, internet will be very confusing.</p>
<hr />
<h2 id="heading-why-dns-records-are-needed">Why DNS records are needed</h2>
<p>DNS is not only one thing. Website need many things like:</p>
<p>website address</p>
<p>email address</p>
<p>who control domain</p>
<p>some verification</p>
<p>So DNS use records DNS is like a folder and records are files inside it.<br />Each record do one work.</p>
<hr />
<h2 id="heading-what-is-ns-record">What is NS record</h2>
<p>NS means Name server NS record tell who will control the domain example:-</p>
<p>chaicode.com -&gt; ns1.cloudfare</p>
<p>This mean Cloudflare control the DNS of this website.</p>
<p>eg:- like telling The house is under the office NS record tell who is boss of domain.</p>
<p>Browser → DNS → Server (high-level flow)</p>
<p>User-&gt;&gt;DNS: Where is <a target="_blank" href="http://example.com">example.com</a>? DNS--&gt;User: It's at 192.0.2.1 User-&gt;Server: HTTP Request to 192.0.2.1 Server--&gt;User: Returns website data</p>
<hr />
<h2 id="heading-what-is-a-record">What is A record</h2>
<p>A record means Address record. It is use to tell the browser what is the IP address of a website When we type a domain name in browser, the browser cannot understand name it only understand number. A record change the domain name into IPv4 address so browser can reach the correct server for eg you can think A record like home address of a person without address nobody can find the house.</p>
<p>eg :- chaicode.com→ 104.21.44.88</p>
<hr />
<h2 id="heading-what-is-aaaa-record">What is AAAA record</h2>
<p>AAAA record is same like A record but it give IPv6 address instead of IPv4. IPv6 is new type of IP address because old IPv4 address are getting finished slowly. Some websites use both A and AAAA record. If browser support IPv6 then it use AAAA record, otherwise it use A record. AAAA record help internet work in future also.</p>
<p>for eg:- chaicode.com → 2606:4700; :6815 : 2c59</p>
<hr />
<h2 id="heading-what-is-cname-record">What is CNAME record</h2>
<p>CNAME record means Canonical Name. It is used when one domain name is pointing to another domain name. For example <a target="_blank" href="http://www.example.com"><code>www.example.com</code></a> can point to <a target="_blank" href="http://example.com"><code>example.com</code></a>. This means both names are same website. CNAME is useful because we do not need to create many A records again and again. It make DNS management more easy.</p>
<p>for eg:- www.pyushsirfullstackaiudemy.com → pyushsirfullstackaiudemy.com</p>
<hr />
<h2 id="heading-what-is-mx-record">What is MX record</h2>
<p>MX record means Mail Exchange record. It is used to decide where the emails of a domain should go. When someone send email to <a target="_blank" href="mailto:name@domain.com"><code>name@domain.com</code></a>MX record tell which mail server will receive that email. Website server and email server are different so MX record make sure email not go to website server by mistake. Without MX record, emails will not work properly.</p>
<p>for eg:- hitesh.aicohort.com → mail.google.com</p>
<p>sequence diagram:</p>
<p>Sender-&gt;DNS: Who handles emails for @<a target="_blank" href="http://example.com">example.com</a>? DNS--&gt;Sender: MX Record: <a target="_blank" href="http://mail.example.com">mail.example.com</a> (Priority 10) Sender-&gt;DNS: What is the IP of <a target="_blank" href="http://mail.example.com">mail.example.com</a>? DNS→Sender: A Record: 198.51.100.1 Sender-&gt;MailServer: delivers Email</p>
<hr />
<h2 id="heading-what-is-txt-record">What is TXT record</h2>
<p>TXT record store simple text information related to domain. It is mostly used for verification and security purpose many services ask to add TXT record to prove that you are owner of domain TXT record is also used for email security like preventing spam you can think TXT record like proof paper of a website.</p>
<p>eg:- take it as an identity card for domain</p>
<hr />
<h2 id="heading-how-all-dns-records-work-together">How all DNS records work together</h2>
<p>For one website many DNS records work together NS record decide who control the DNS A and AAAA record tell where the website server is CNAME record handle other names of website MX record manage emails and TXT record help in verification and security. All records have different work but together they make website and email work smoothly.</p>
]]></content:encoded></item></channel></rss>