This discussion about terminology has gotten rather pedantic. The
wikipedia article cited previously states the following example:

" and are subdomains of the domain, which in turn is a subdomain of the 'com'
top-level domain."

Are Charles and Ken suggesting that is not a
subdomain of

Charles suggested that might point to a
publicly addressed "server". Jeff indicated that pointed to the IP address of a "firewall" in
his office.

I will go with Jeff on this because I have never known of any
organization ever assigning a public IP address to a "server".
Instead, they assign a public IP address to a network device
(gateway/router/firewall) in their control which may further route to
other network devices in their control, which may ultimately route to
a "server" in their control.

It appears that some of the terminology confusion in this discussion
may have been a result of how one views internal "names" and "routing"
mechanisms within internal networks vs. how names and routing is done
via public DNS. For example, a company may set up a web proxy on an
internal network which routes to a web
server on the other side of the planet. But that routing is not based
on DNS.


This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page