Welcome to www.msunderestimated.com

Web Hosting - The Internet and How It Works In one sense, detailing the statement in the title would require at least a book. In another sense, it can't be fully explained at all, since there's no central authority that designs or implements the highly distributed entity called The Internet. But the basics can certainly be outlined, simply and briefly. And it's in the interest of any novice web site owner to have some idea of how their tree fits into that gigantic forest, full of complex paths, that is called the Internet. The analogy to a forest is not far off. Every computer is a single plant, sometimes a little bush sometimes a mighty tree. A percentage, to be sure, are weeds we could do without. In networking terminology, the individual plants are called 'nodes' and each one has a domain name and IP address. Connecting those nodes are paths. The Internet, taken in total, is just the collection of all those plants and the pieces that allow for their interconnections - all the nodes and the paths between them. Servers and clients (desktop computers, laptops, PDAs, cell phones and more) make up the most visible parts of the Internet. They store information and programs that make the data accessible. But behind the scenes there are vitally important components - both hardware and software - that make the entire mesh possible and useful. Though there's no single central authority, database, or computer that creates the World Wide Web, it's nonetheless true that not all computers are equal. There is a hierarchy. That hierarchy starts with a tree with many branches: the domain system. Designators like .com, .net, .org, and so forth are familiar to everyone now. Those basic names are stored inside a relatively small number of specialized systems maintained by a few non-profit organizations. They form something called the TLD, the Top Level Domains. From there, company networks and others form what are called the Second Level Domains, such as Microsoft.com. That's further sub-divided into www.Microsoft.com which is, technically, a sub-domain but is sometimes mis-named 'a host' or a domain. A host is the name for one specific computer. That host name may or may not be, for example, 'www' and usually isn't. The domain is the name without the 'www' in front. Finally, at the bottom of the pyramid, are the individual hosts (usually servers) that provide actual information and the means to share it. Those hosts (along with other hardware and software that enable communication, such as routers) form a network. The set of all those networks taken together is the physical aspect of the Internet. There are less obvious aspects, too, that are essential. When you click on a URL (Uniform Resource Locator, such as http://www.microsoft.com) on a web page, your browser sends a request through the Internet to connect and get data. That request, and the data that is returned from the request, is divided up into packets (chunks of data wrapped in routing and control information). That's one of the reasons you will often see your web page getting painted on the screen one section at a time. When the packets take too long to get where they're supposed to go, that's a 'timeout'. Suppose you request a set of names that are stored in a database. Those names, let's suppose get stored in order. But the packets they get shoved into for delivery can arrive at your computer in any order. They're then reassembled and displayed. All those packets can be directed to the proper place because they're associated with a specified IP address, a numeric identifier that designates a host (a computer that 'hosts' data). But those numbers are hard to remember and work with, so names are layered on top, the so-called domain names we started out discussing. Imagine the postal system (the Internet). Each home (domain name) has an address (IP address). Those who live in them (programs) send and receive letters (packets). The letters contain news (database data, email messages, images) that's of interest to the residents. The Internet is very much the same.

Helpful Hints on Getting Better Respect in the Workplace Sometimes, an inhospitable work atmosphere can ruin the best job in the world. If you work in an office where people don’t respect each other and you feel undervalued and taken advantage of, then you are likely to give up and move on--no matter how much you love the work. When people work closely together, disagreements and problems are bound to arise from time to time. There are, however, ways you can get more respect in the workplace, so you don’t have to dread heading to the office every morning. As the old adage goes, you have to give respect to get respect. Are you doing everything you can to treat your co-workers with dignity and respect? Put another way, are you doing everything you can to avoid annoying everyone in the office? There are a lots of little ways you can make the day more pleasant for everyone, including showing up on time for work and for in-house meetings, not talking too loudly on the phone, keeping your personal cell phone ringtone on silent or vibrate, and cleaning up when you use the common break rooms and kitchen area. Things like spamming everyone in the office with incessant “funny” emails, sending political or religious emails (or challenging everyone on political or religious issues), or invading privacy by looking at someone else’s emails, phone messages, or mail are also not a good idea in the office setting. Then there are the big ones – you should never take credit for someone else’s work, talk behind people’s backs, lie, steal from other’s desks (even if it is just a post-it note or white-out), or have a general bad argumentative attitude. If you are doing anything of these things, trying to correct your own behavior is the first step to earning a little more respect in the workplace. What happens if you are doing everything you can and you still aren’t getting the respect you feel you deserve in the office? How you handle things may partly depend on who is showing you the disrespect. Are your subordinates treating you like you’re not the boss? In this case, having a little one on one conversation might do the trick. It doesn’t have to confrontational. You can simply point out that you are getting the impression that they may be having a little trouble with your leadership style and offer them a chance to raise any problems. If they bring up a legitimate problem, then there is something you can work on to make things go smoother in the future. If they can’t point to any one thing, let them know politely, but firmly, what you will need from them going forward in terms of respect. And then, stick to it and hold them accountable for their behavior. If your boss is not respecting you, things can get a little trickier. If your boss has a bad attitude, being pulled up on it by his subordinates is probably not going to do much to improve it. Your company may have a grievance policy in place to deal with issues like this, and it is best to go down this path when dealing with a boss with a respect issue. There are some respect issues in the work place that can’t be resolved with the softly, softly approach. If you are being persecuted on the basis of your gender, your race, your disability, or your sexual preference, you have a right to demand a stop to that at once. If the abuse is coming from your co-workers, go straight to your boss. If your boss is unresponsive, or if your boss is the offender, go right over their head, and keep going until you get some satisfaction.

Web Hosting - DNS, How The Internet Keeps Track of Names The way computers communicate is, in a way, very similar to something very familiar: the postal system that delivers letters and packages. Here's how... The Internet is just what the name suggests, a large inter-connected set of networks. But those networks are pointless without the one part that forms what is called their 'end-nodes', otherwise known as computers. Those computers often need to share information because the people who use them want to share information. But, in a system where there are millions of separate computers, how can you enable them all to communicate? One very important feature of that solution is performed by something called DNS, the Domain Name System. Every part of a network that is going to send or receive information is assigned an IP address. That's a numeric identifier that uniquely specifies a particular 'node', such as a computer, a router that directs traffic or other component. They look like this: 209.131.36.158 But those numbers are more difficult for people to remember and work with. They also aren't very attractive from a marketing perspective. So, a naming system was layered on top of some of them, mostly the computers involved, though routers have names, too. But once you have a system that associates a unique IP address to a given name, you need some way of keeping track of all of them. That's carried out by several different pieces of the system: Name Registrars, DNS Servers and other components. The Name Registrars, overseen by IANA (Internet Assigned Numbers Authority) and other international bodies, provide and keep track of domain names. When you register with GoDaddy or any of a hundred other intermediate companies, ultimately that information makes its way into a number of specialized databases stored inside DNS Servers. A DNS Server is the hardware and/or software that tracks and forwards the IP Address/Domain Name pair from one place to the next. In many cases, there are a number of them between your browser and the remote computer you want to share information with. Suppose you request information from, say, Yahoo's site by clicking on a link on their site. DNS resolves (translates) the name of WHO IS making the request and OF WHOM, to addresses, then passes the request through the network to the requested IP address. The requested data is then passed back through the mesh of network components to your computer and displayed in your browser. Whether the communication is between a desktop computer and a server somewhere, or between one server and another, the process is essentially the same. DNS servers translate names into IP addresses and the requests for data are forwarded on. In some cases those DNS servers are part of a specialized network computer whose sole job is to do the translation and forwarding. In other cases the DNS software may reside on a server that also houses a database of general data, or stores email, or performs other functions. But however complicated the chain or the parts, the basic process is simple. Translate the name to an address, just as the postal system does. Whether international or local, your name is associated with an address, and the deliveries are made to the address, then forwarded to a particular name.