TheHum wrote
at the network layer, if a computer uses a web browser to request a web page using a URL will the destination ip address be that of the web server?

Yeah, the destination IP is where you're (attempting) to connect. This goes for more than just the web browser, but in your case you have it right.

TheHum wrote
Also when does DNS actually happen, is it before the encapsulation process has begun?
Which would mean the URL is typed in, a DNS request is sent to the DNS server and then once the IP address of the web page is received the encapsulation process for the page begins(which is sent to the web server)

I'm a little confused by your question. In the event that you're connecting to any remote server (lets call this sever TTG), you'll partake in encapsulation. Before connecting to TTG, your request is going to be handed down through multiple layers. Some add a header, one adds a packet and so on until you're transmission is fully encapsulated and ready to be sent. DNS would require connecting to a name server, in which encapsulation is required. Then, once your destination IP is resolved, encapsulation will occur again to connect to the destination IP given to you by the resolver (TTG). So I guess technically DNS occurs before the encapsulation process, in the sense that there are two separate occurrences, with DNS encapsulation falling before the encapsulation process for the site you're connecting to.


Hopefully that made sense. I'm no CCNA or anything so I'm going off what my interpretation of your question was.

Saki wrote

TheHum wrote
at the network layer, if a computer uses a web browser to request a web page using a URL will the destination ip address be that of the web server?

Yeah, the destination IP is where you're (attempting) to connect. This goes for more than just the web browser, but in your case you have it right.

TheHum wrote
Also when does DNS actually happen, is it before the encapsulation process has begun?
Which would mean the URL is typed in, a DNS request is sent to the DNS server and then once the IP address of the web page is received the encapsulation process for the page begins(which is sent to the web server)

I'm a little confused by your question. In the event that you're connecting to any remote server (lets call this sever TTG), you'll partake in encapsulation. Before connecting to TTG, your request is going to be handed down through multiple layers. Some add a header, one adds a packet and so on until you're transmission is fully encapsulated and ready to be sent. DNS would require connecting to a name server, in which encapsulation is required. Then, once your destination IP is resolved, encapsulation will occur again to connect to the destination IP given to you by the resolver (TTG). So I guess technically DNS occurs before the encapsulation process, in the sense that there are two separate occurrences, with DNS encapsulation falling before the encapsulation process for the site you're connecting to.


Hopefully that made sense. I'm no CCNA or anything so I'm going off what my interpretation of your question was.

Okay thankyou that did make sense and helped me a lot! you the real MVP