Welcome to www.mypickletalksautism.com
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: 22.214.171.124
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.
Copyright lawyer guild What exactly is a copyright lawyer guild? A copyright lawyer guild is just like any other guild, it a is club just for copyright lawyers. Many times you can find a list of names of all the copyright lawyers that have joined, as well as all their contact info and if they have a website or not. Sometimes you will have to be invited to join, while others it is free for you to look around. However as a guest you may only be able to view certain information, once you pay though you?ll get to look at all the goodies the guild holds. There will most likely be a select amount of newsletters put out by the guild, the number depends on the guild itself and how many they want. In a way this is very much like a writer?s guild, you will have a list of every writer in a certain state and their information about them. Any client can find a copyright lawyer?s guild online, this is basically a site that lists all types of information about copyrights, cases, lawyers, releases and much more. A client may even find out if the their copyright lawyer has been acknowledged for any special awards in the at-a-guy section, not all have this but most will. There will probably be a lot of articles on copyright issues and might explain to you what it is you need. You can also find cases that are currently going on and others that have already been through trial, this is a great way to stay up to date with all the latest copyrighting issue. If you are lawyer it is great so you always know what is going on and what is being added to the laws that already exist. One may even find a forum inside an online copyright lawyer?s guild; this opens doors to both clients and lawyers. A lawyer may be able to find help in an area they aren?t 100% about and a client is able to ask for help without being charged. A copyright lawyer guild may also be a group that meets every couple of months at a restaurant, office or a number of different places to discuss things. Topics may include things they are dealing with, cases in the press or inside the office, or hot topics in the field. How to help a client that is upset, how to use etiquette in emails, etc. They may watch a short film on copyrights and how they effect the business. There may be a few seminars that they are invited too or asked to actually give speeches at, the topics are endless but will all reflect on their field of expertise. Guilds are a great way for a person to meet and greet others in their profession and share stories or experiences with one another. Not all copyright lawyer guild list every lawyer, only those that pay for membership are. Which means if your lawyer hasn?t paid his dues than he won?t be listed, however this doesn?t make him a bad lawyer. Your lawyer may just be starting up and hasn?t got around to joining a guild or if he?s been around for a while maybe he hasn?t had much luck in finding clients through guilds and would rather do it the way he?s been doing it.
Web Hosting - Redundancy and Failover Among the more useful innovations in computing, actually invented decades ago, are the twin ideas of redundancy and failover. These fancy words name very common sense concepts. When one computer (or part) fails, switch to another. Doing that seamlessly and quickly versus slowly with disruption defines one difference between good hosting and bad. Network redundancy is the most widely used example. The Internet is just that, an inter-connected set of networks. Between and within networks are paths that make possible page requests, file transfers and data movement from one spot (called a 'node') to the next. If you have two or more paths between a user's computer and the server, one becoming unavailable is not much of a problem. Closing one street is not so bad, if you can drive down another just as easily. Of course, there's the catch: 'just as easily'. When one path fails, the total load (the amount of data requested and by how many within what time frame) doesn't change. Now the same number of 'cars' are using fewer 'roads'. That can lead to traffic jams. A very different, but related, phenomenon occurs when there suddenly become more 'cars', as happens in a massively widespread virus attack, for example. Then, a large number of useless and destructive programs are running around flooding the network. Making the situation worse, at a certain point, parts of the networks may shut down to prevent further spread, producing more 'cars' on now-fewer 'roads'. A related form of redundancy and failover can be carried out with servers, which are in essence the 'end-nodes' of a network path. Servers can fail because of a hard drive failure, motherboard overheating, memory malfunction, operating system bug, web server software overload or any of a hundred other causes. Whatever the cause, when two or more servers are configured so that another can take up the slack from one that's failed, that is redundancy. That is more difficult to achieve than network redundancy, but it is still very common. Not as common as it should be, since many times a failed server is just re-booted or replaced or repaired with another piece of hardware. But, more sophisticated web hosting companies will have such redundancy in place. And that's one lesson for anyone considering which web hosting company may offer superior service over another (similarly priced) company. Look at which company can offer competent assistance when things fail, as they always do sooner or later. One company may have a habit of simply re-booting. Others may have redundant disk arrays. Hardware containing multiple disk drives to which the server has access allows for one or more drives to fail without bringing the system down. The failed drive is replaced and no one but the administrator is even aware there was a problem. Still other companies may have still more sophisticated systems in place. Failover servers that take up the load of a crashed computer, without the end-user seeing anything are possible. In fact, in better installations, they're the norm. When they're in place, the user has at most only to refresh his or her browser and, bingo, everything is fine. The more a web site owner knows about redundancy and failover, the better he or she can understand why things go wrong, and what options are available when they do. That knowledge can lead to better choices for a better web site experience.