Welcome to taxkingsandqueens.com

Web Hosting - Why Backups Are Essential One thing most web site owners have little time for is... anything! Anything other than focusing on their site content and the business or service it supports and the information it provides, that is. That means that administration often suffers, as it frequently must. There's only so much time in the day. But the one thing that you should never let slide are backups. They are like insurance. You rarely need it (you hope), but when you do you need it very badly. Performing regular backups - and testing them - doesn't have to be a nightmare. A little bit of forethought and effort and they can be automated to a high degree. And, they should be tested from time to time. Even when a backup appears to have gone without a hitch, the only way to know whether it's of any value is to attempt to restore the information. If it can't be restored, the backup is worthless. Even when the web hosting company provides the service, there is still some planning involved for the site owner. Hosting companies often rely on one or both of two methods. They backup everything (called a full backup), then backup anything which has changed since the last full backup (called an incremental backup). Of special interest are any configuration files that have been tailored. If you've modified the default installation of a software package, you want to be able to recapture or reproduce those changes without starting from scratch. Network configuration files, modifications to basic HTML files, CSS style sheets and others fall into the same category. If you have XML files, databases, spreadsheets or other files that carry product or subscriber information - about items purchased, for example, or people who signed up for a newsletter - those should get special attention, too. That's the lifeblood of your business or service. Lose them and you must start over. That can break your site permanently. It should go without saying that all HTML and related web site files that comprise visible pages should be backed up regularly. It isn't necessary to record every trivial change, but you can tailor backup software to exclude files or folders. Usually they're so small it isn't worth the trouble. But in some cases those small changes can add up in scenarios where there are many thousands of them. Here again, the backups are worthless if they can't be used. Even if the hosting company charges for doing so, it's worthwhile to test once or twice a year at least to ensure the data can be restored. That's especially true of database backups, which often involve special software and routines. Database files have a special structure and the information is related in certain ways that require backups be done differently. Developing a backup strategy can be straightforward. Start simply and review your plan from time to time, modifying it as your site changes and grows. But don't neglect the subject entirely. The day will come when a hard drive fails, or you get hacked or attacked by a virus, or you accidentally delete something important. When that day comes, the few minutes or hours you spent developing and executing a backup plan will have saved you days or weeks of effort.

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.

Copyright Infringement Play It Safe: Making Sure You're Not Committing Copyright Infringement Copyright infringement is not an easy thing to explain. While it may seem as simple as not using someone else’s work, it’s not that easy. Thanks to the Electronic Frontier Foundation, and many other organizations, we have the ability to use others’ works – as long as we use it under ‘fair use’ laws. So what does fair use have to do with copyright infringement, and how can you utilize it? Fair use laws are the conditions in which you can use a copyrighted work without having to pay someone royalties. This includes when you use a copyrighted work for educational or instructional uses, criticism of the work, commentaries on the work, news reporting about the work, teaching on the work (including multiple copies for classroom use), scholarship uses, and research. This is talked about fully in Section 107 of the Copyright Code (commonly called Fair Use) and is available for you to read at your local library. Copyright Infringement in day-to-day life Sometimes, if you’re writing a paper for work or school, or if you are creating a Power Point presentation, you need to use someone’s work that is already in copyright. So how do you use it without committing copyright infringement? All you have to do is ask – the worst they can say is no, right? But, if they do say no, there are several items in the public domain which may help you to finish your project without having to commit copyright infringement. What is the public domain, and how does it relate to copyright infringement? Material that is not copyrighted is considered in the public domain – you cannot commit copyright infringement on works in the public domain. These works include things that the copyright has expired on, or is not copyright-able – such as government publications, jokes, titles, and ideas. Some creators (writers, musicians, artists, and more) deliberately put their work in the public domain, without ever obtaining copyright, by providing an affiliation with Creative Commons. Creative Commons allows people who create materials to forfeit some, or all, of their copyright rights and place their work either partially or fully in the public domain. So, how do I ensure I’m not committing copyright infringement? First of all, if you’re going to use someone else’s material, you may want to check the public domain to see if something is suitable for use, instead of trying to use someone else’s copyright. However, if you can’t find something suitable (and you can’t create something yourself), the next best thing (and your only legal course of action) is to find a piece that is in copyright, and contacting the copyright holder. When you contact the copyright holder, make sure you tell them what you want to use their piece for – whether it’s for your blog, podcast, or report – and ask them if you can use it. You may have to pay royalties, or an attribution in your piece, or a combination of both. The creator may also place many limitations on when and how you can use their material. Follow all these instructions they give you, and you’ll be free and clear to use their work as you want. Once you have permission to use a copyrighted work, you need to make sure you stay within the agreed-upon boundaries - if you veer outside their agreed terms, you may open yourself up for a copyright infringement lawsuit – which can be nasty, costly, and time consuming. If you’re in doubt, before contacting the copyright holder, contact a copyright lawyer to ensure you’re following the law – and protect yourself!