Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialNiall O Laoghaire
1,821 PointsDNS & TCP/IP
HI there, loved the course - one thing I'm confused about- when you type a url in a browser is the first thing to happen that the url resolves to an ip address vis DNS & then this Ip address is included in the internet protocol layer & only then can the packets of info be transmitted across the routers?
3 Answers
Caleb Kleveter
Treehouse Moderator 37,862 PointsYep, that's correct!
Omahr B. Carpinteyro
Front End Web Development Techdegree Student 4,684 PointsSo, as I understand... the process is:
Client -> DNS -> Client -> Server -> Client
Declan Ward
2,008 PointsI thought the DNS 'forwarded' the request, thus being....
Client -> DNS -> Server -> Client. ????
Christopher Branscum
1,730 PointsAccording to the teachings of one STUNNING! Joy, the process goes like:
CLIENT--> DNS--> SERVER (INPUT ROUTE) and then, from..... SERVER--> CLIENT (OUTPUT ROUTE) --B/C the IP address does not require translation back through the DNS to get back to the CLIENT (YOU!)