Welcome to www.pricelesswarehome.org
Web Hosting - Domain Name Changes and How They Affect You
New domain names are registered all the time, and ones previously registered expired. Sometimes that's the result of simple neglect. The owner of the name chose not to renew his or her ownership, so the name became available for someone else to use. In rare cases, a highly original mind managed to think of a new one. In the other common scenarios, someone chose to just let it go or sell it.
When you choose to change your domain name, there are actually two separate steps involved: releasing the old name, and adopting the new one. But, just as the postal system can have difficulty forwarding your letters when you change your personal name, changing your domain name brings certain difficulties.
One of the most prominent is the fact that any name change requires a change to thousands of DNS Servers around the globe. DNS (Domain Name System) is the set of software/hardware components that allows domain names to map to IP addresses. IP addresses are what are actually used 'under the covers' when one computer communicates with another.
Note that there isn't always a 1:1 correspondence between a name and an IP address. One IP address can serve multiple domain names and one domain name can have multiple IP addresses. For the sake of simplicity, we'll stick to the common case here.
DNS servers around the world maintain internal databases that match the name to an IP address. Not all servers have all pairs of names/addresses. A series of complex routines allows a request to be forwarded when the particular DNS server doesn't have a needed record. When you acquire a domain name that used to be associated with a given IP address, the odds of you acquiring the same IP address are extremely low.
In the unlikely case, for example, that you acquired the domain name yahoo.com, you would almost certainly not get the IP address that was matched with it (unless you bought the Yahoo! company). So, as a result of the change, the name/IP address pair is no longer what it was.
A similar circumstance exists when you retain your IP address, but want to change the domain name associated with it. In either case, the pairing has changed.
The catch is this: when the change takes place, those DNS databases are not all updated instantaneously around the world.
Even apart from the limited speed with which computers and networks operate, (and neglecting the human factor if/when the change is made manually to more than one server) the reason is something called caching.
In order to communicate efficiently, DNS servers are designed to assume that changes will be relatively rare. Just as with the postal system, you don't move your address or change your name every minute. Since that's true, in general, the name/IP address pair is cached. A cache is a set of stored information that is reused so that fresh information doesn't have to be communicated with every request for a web page or data.
A chain of DNS servers pass requests to the last known address. There is usually more than one system between your computer and the server you want to communicate with. Most of the time, that's your current name/address. When you change the name, that pair is no longer valid. In order to propagate the new name/address pair (so the terminology goes), that cache has to be refreshed.
Something similar happens when you establish an entirely new name. That name is first associated with an IP address and that pair has to be communicated to DNS servers around the world in order for you to be able to reach any one of them at random.
But DNS servers don't do that until they are requested to do so by your action of asking for information from a remote server. Because of that, but chiefly because of caching, it can take quite a while for the new pair to become known around the Internet. Caches can expire and get refreshed in a few minutes or a few hours. It varies.
That time can be as short as an hour or less, if the path between your computer and the web server is very simple and only one DNS server needs to be updated. Or, it can take up to 48 hours or more. Though the 'official' range is often given by registrars as 24-48 hours, the average is closer to about six hours. But that's an average. The actual time in any given case can (and does) vary widely.
In the meantime, a number of effects can occur. The most obvious is that, since the name/IP address pair can't be resolved properly, you don't reach the server you want. Your browser points to the old one (in the rare case it's still accessible by that name and address), or it simply reports there's no such name at that address.
So, when registering a new name or buying an old one, you should establish the site, but not advertise it for at least a couple of days. Better to wait to get visitors than to turn them off by being 'not at home' when they call.
Definition of copyright infringement Protect Yourself: Know the Definition of Copyright Infringement As you?re creating something, you may wonder what copyright infringement actually is. It?s necessary, if you?re creating a work ? albeit written, musical, videos, software or some other form ? that you know the definition of copyright infringement. This issue is very complicated, and not very easily spelled out in plain English, so please make sure that if you?re ever unsure to contact a copyright lawyer immediately to ensure you?re using copyrights in a legal method appropriate to the medium. As I mentioned earlier, a definition of copyright infringement is difficult, at best. Copyright infringement is defined by the jurisdiction ? the United States of America has different copyright laws than the United Kingdom, or Australia, or Russia, or even China. Because of this fact, you should first, before anything else, check the laws in your jurisdiction (country, city & province) before using something that isn?t in the public domain. For our definition of copyright infringement, the public domain is a place where works are that aren?t copyright-able. Works that aren?t copyright-able include ideas, works that aren?t eligible (150 years-old documents, or older ? think Beethoven and Frankenstein), data that isn?t categorized in a creative way (this could be a database, such as a phone book or other publicly-accessible data), or items that the owners have specified creative commons copyrights. As you can see, copyright law is rather complicated. Wikipedia.org gives us the definition of copyright infringement as: ?Copyright infringement (or copyright violation) is the unauthorized use of material that is protected by intellectual property rights law particularly the copyright in a manner that violates one of the original copyright owner's exclusive rights, such as the right to reproduce or perform the copyrighted work, or to make derivative works that build upon it. The slang term bootleg (derived from the use of the shank of a boot for the purposes of smuggling) is often used to describe illicitly copied material.? Our definition of copyright infringement includes the works of creative commons. Creative commons is an organization that allows for the copyright author to determine the uses available for people who want to use their works ? for such items as for audio, images, video, text, educational materials, and software. It allows for the copyright owner to allow people to use their works for non-commercial, commercial, no derivatives, share alike, or just by giving attribution. Creative Commons is a license granted by the copyright holder, and can be used in both online (electronic internet) works and offline works. There are many places you can go to get a definition of copyright infringement. The most reliable definition of copyright infringement would be from your local copyright lawyer ? they will know exactly what in your jurisdiction is legal or not, and how you can use other peoples? works or protect your own. The real definition of copyright infringement comes from your jurisdictions statutes. In the United States of America, our jurisdiction?s copyright laws are contained in Title 17 of the United States Code, §501 - §513. You can also find a definition of copyright infringement through such organizations such as the European Union or World Trade Organizations. While s legal country or organizational definition of copyright infringement is hard for the layperson to understand, a copyright lawyer will help you to figure out what it is that your work needs to be protected against copyright infringement, or to protect yourself if you intend to use the work of another writer, director, or musician.
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.