web browser and DNS connections

  • Thread starter Thread starter Ken
  • Start date Start date
K

Ken

I want to clarify when people request a page in http://mydomain.com in
the web browser, what is the entire storyboard before displaying the
page in the web browser.

here's the steps, please advise if I miss something.

1) user type http://mydomain.com in the web browser
2) the web browser will connect to WHOIS database to look up the naming
server
for http://mydomain.com
3) the web browser connect to the naming server and request the IP
address for http://mydomain.com
4) the naming server returns the IP address of http://mydomain.com to
the web browser
5) the web browser makes a connection to the IP address and request for
the page.

Please advise.

thanks!!
 
Ken said:
I want to clarify when people request a page in http://mydomain.com in
the web browser, what is the entire storyboard before displaying the
page in the web browser.

here's the steps, please advise if I miss something.

1) user type http://mydomain.com in the web browser
2) the web browser will connect to WHOIS database to look up the naming
server
for http://mydomain.com
The Browser (or your OS to be more specific) connects directly to the
DNS Server. Enter "ipconfig /all" to see your DNS Servers, or ifconfig
(when using linux).
3) the web browser connect to t
he naming server and request the IP
It requests the A-Record in DNS, there is the IP
4) the naming server returns the IP address of http://mydomain.com to
the web browser
5) the web browser makes a connection to the IP address and request for
the page.
yes, but very important, the adress www.mydomain.com ist entered in the
Host-Header of the http-request (HTTP 1.1).
Otherwise you get maybe an other page if you access the website with the
ip-adress instead of the domain name.
Please advise.

thanks!!
no problem.

cheers,
Stefan
 
Stefan said:
The Browser (or your OS to be more specific) connects directly to the
DNS Server. Enter "ipconfig /all" to see your DNS Servers, or ifconfig
(when using linux).

need more clarifications on how the web browser connects to DNS servers
for IP address lookup?

My understanding is that each web site associates with different DNS
servers, thats why when we register a new domain name, we need to make
sure the DNS server information. Correct concept?

Therefore, when I type http://mydomain.com in the web browser, the OS
will first connect to my DNS servers (ipconfig /all) to find out the
DNS servers of http://mydomain.com. Next it will look up the IP address
of http://mydomain.com in DNS server of http://mydomain.com, and return
the IP address to the web browser. Finally, the web browser will do a
HTTP request to the IP address directly.

Please advise more. thanks!!
 
Ken said:
need more clarifications on how the web browser connects to DNS servers
for IP address lookup?

The browser probably does NOT connect directly to the DNS server,
but rather uses a system call to request the resolution and the built
in RESOLVER does that connection -- it may use the local DNS
cache, or if the name is not available there or there is not such local
DNS cache, then the resolver will ask the DNS server to resolve the
name.

Once resolved, the answer is returned to the (web) application and
the connection is then made to that IP address using the HTTP protocol.
(Unless it is SSL in which it will use HTTPS but the underlying
client-server protocol remains the same.)
My understanding is that each web site associates with different DNS
servers, thats why when we register a new domain name, we need to make
sure the DNS server information. Correct concept?

More or less correct: Each domain or zone is held on some DNS server
(sometimes the same, sometimes different servers for different zones) --
not each web server. You might have several web servers all listed
in the same zone (on the same DNS server set.)
Therefore, when I type http://mydomain.com in the web browser, the OS
will first connect to my DNS servers (ipconfig /all) to find out the
DNS servers of http://mydomain.com.

Right. The DNS RESOLVER is the portion of the OS that does this.

Except this is usually done withing a "connection" but rather a simple
UDP request (all in one message)...
Next it will look up the IP address
of http://mydomain.com in DNS server of http://mydomain.com,

So this portion is usually combined with the previous step (there are
not two steps involved with UDP.)
and return
the IP address to the web browser. Finally, the web browser will do a
HTTP request to the IP address directly.

Correct.
 
In
Ken said:
I want to clarify when people request a page in http://mydomain.com in
the web browser, what is the entire storyboard before displaying the
page in the web browser.

here's the steps, please advise if I miss something.

1) user type http://mydomain.com in the web browser
2) the web browser will connect to WHOIS database to look up the
naming server
for http://mydomain.com
3) the web browser connect to the naming server and request the IP
address for http://mydomain.com
4) the naming server returns the IP address of http://mydomain.com to
the web browser
5) the web browser makes a connection to the IP address and request
for the page.

Please advise.

thanks!!

In addition to the other responses, see if this diagram helps:

ZoneEdit.Com Simplified example of how DNS works (ZoneEdit.com):
http://www.zoneedit.com/doc/dns-basics.html

How Does DNS Work - DNS Wizard:
http://www.dnswiz.com/dnsworks.htm

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If you are having difficulty in reading or finding responses to your post,
instead of the website you are using, I would suggest to use OEx (Outlook
Express or any other newsreader of your choosing), and configure a newsgroup
account, pointing to news.microsoft.com. This is a direct link into the
Microsoft Public Newsgroups, and it is FREE and DOES NOT require a Usenet
account with your ISP. With OEx , you can easily find your post and watch &
track threads, sort by date, poster's name, watched threads or subject.

Not sure how? It's easy and you'll enjoy it
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile.
Infinite Diversities in Infinite Combinations.
=================================
 
Question: Customers Domain Name on Win2000 Server is the same as their
external www website (off site). Problem: When domain users try to access
the external www website they are brought back to the local IIS server which
states "Website Under Construction". How should DNS be configured to get
lookups to the external website. We are not able to just use the websites IP
address.
 
KLI-MS said:
Question: Customers Domain Name on Win2000 Server is the same as their
external www website (off site). Problem: When domain users try to
access
the external www website they are brought back to the local IIS server
which
states "Website Under Construction". How should DNS be configured to get
lookups to the external website. We are not able to just use the websites
IP
address.

This only happens if they use the "bare domain name" without
the WWW (or other server name) prefix.

Teach internal users to use the full WWW.domain.com name.

External users can still use either this or the bare domain.com
name.

And it's easier to type the full thing anyway as long as it is a
dot-com since they can type "domainname<ctrl-enter>" in
most browsers.
 
In
KLI-MS said:
Question: Customers Domain Name on Win2000 Server is the same as
their external www website (off site). Problem: When domain users
try to access the external www website they are brought back to the
local IIS server which states "Website Under Construction". How
should DNS be configured to get lookups to the external website. We
are not able to just use the websites IP address.

Simple. One of two choices:
1. Under the internal zone, create a www entry, provide the actual external
IP address of the webserver.

2. If the web hosting company is using BigIP or any other type of webfarm
and there are multiple IPs:
Rt-click your internal zone, choose new delegation.
Provide the SOA name servers' name and IP addresses.

To access it by http://domain.com would be a little more difficult because
you don't want to mess with that record in an AD domain. It's called the
LdapIpAddress and is used by the GetGpoList function and DFS. You can get
around that by creating a website on EACH domain controller, and in the
website properties, provide a redirect to www.domain.com, of course ONLY
after you've performed step 1 or 2 above.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.

Not sure how? It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile.
Infinite Diversities in Infinite Combinations.

The only thing in life is change. Anything less is a blackhole consuming
unnecessary energy.
===========================
 
Back
Top