Welcome to www.minisinbox.com

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.

Web Hosting - FTP and Other File Transfer Tools Anything related to the Internet or computers is bound to introduce technical issues pretty soon. One of the earliest that novice web site owners encounter is FTP, which is an acronym for File Transfer Protocol. Seeing it spelled out, it's easy to see why those in the know quickly move to speaking in short hand. The reason web site owners soon will (or need to) become familiar with FTP is obvious to anyone who has built a site on a remote server. You have to have some way of getting the files to the remote computer and FTP is one of the most common tools. It's also one of the simplest and most efficient. FTP is composed of two parts: the client software and the server software. It's similar, in a way, to talking to someone on the phone who writes down everything you say. You (the client) make a request ('transfer this file to the server') and the listener (the server) takes the request and acts on it. That request to copy a file from a local computer to the remote one is carried out (often 'under the covers') by a PUT command, as in PUT this there. You create the web page (in the form of a file) and then PUT the file on the server. To move a file in the opposite direction, from the remote server to your local computer, your client software issues a GET command. Many FTP clients have graphical interfaces, similar to Windows Explorer, that allow you to drag-and-drop or otherwise copy the file without ever seeing the actual commands that carry it out. But it's helpful sometimes to know what goes on underneath. In tricky cases it can be an advantage to use a command line interface (in Windows, the 'DOS box', with a similar interface familiar to most Linux users). Knowing the commands and being able to use them in the command line form can sometimes help you diagnose what is going on when the graphical tools misbehave. But FTP is not the only way to get a file from here to there. In fact, your browser moves files around from a remote computer to your local one all the time. In most cases, when you type in or click on a URL, what happens under the covers is in essence a file transfer process. The web page is transferred from the web server to your local computer then displayed by the browser. Alternatively, you can sometimes even email a web page/file from your local computer to the remote server, then use an email client on the server itself to get the file and put it in a folder. That requires that you have some form of access to the remote computer. But there are many ways of doing that, such as in-built utilities in the operating system or using commercial remote control programs. Those alternatives can be helpful to know in cases where the FTP file transfer process is misbehaving. Having more than one way to accomplish the task helps you diagnose what might be going wrong. It also helps you get the job done when the usual tools aren't cooperating. The more you learn about these sometimes puzzling acronyms, the easier you can accomplish your own goals.

Copyright infringement insurance coverage Do You Need Copyright Infringement Insurance Coverage? People are creating more content now than ever: eBooks, blogs, web journals, MySpace Pages, Podcasts. Every where, in abundance, you’ll find people sharing their ideas and opinions, and creating entertainment for everyone. However, with all the resources available to us, how can we be sure that we’re not violating copyright law? Should we have copyright infringement insurance coverage? Copyright infringement is the act of using someone else’s copyrighted material – in any form – in our own use without proper allowances. In order to be allowed to use the material, all we may need to do is ask and give the owner royalties, attribution, or some combination thereof. But, occasionally, it’s easy to forget that we need to ask before we use something without rights. You’re allowed to use copyrighted works in a number of forms – educational and instructional uses, parody, commentary, and news are all forms where you don’t need to ask for use – it’s considered fair use under the copyright law. However, even if you’re using the item of copyright in one of these forms, it would still be wise to inform the owner of your intent before using it. Of course, you should contact a copyright lawyer before using anyone else’s work(s), but to keep yourself safe, copyright infringement insurance coverage may be a good bet for you and your colleagues. Should you have copyright infringement insurance coverage? Although this is a new concept, it is one we should look at closely as creators. A well-known adage “there is no completely original idea” comes into play in our current age – while it’s entirely possible for us to have a thought, and act upon the thought – there may be, somewhere, someone who has created close to the same material as we have, without our knowing. Did we create it first? Did they? Would they be able to sue you for copyright infringement? These are the things to ponder as we create our media – should we have copyright infringement insurance coverage? What is copyright infringement insurance coverage? This coverage would be insurance for covering the cost to settle lawsuits brought in regards to copyright infringement – it would be a small amount of coverage. For example, you would only need around $5,000 to cover the court and attorney fees associated with a case, if a suit were brought against a person. Theoretically, you would only pay under $25 per year and would cover up to the five thousand dollar settlement should a case be brought against you. How would you use copyright infringement insurance coverage? Hopefully, you’d never have to use your copyright infringement insurance coverage. But, it would be there in case a charge was ever brought to you on copyright infringement With so many of us – bloggers, columnists, podcasters – creating our own content, it’s in our best interest to consider something such as this. We may not always get the rights we need in order to use a work, either whole or in part. As you can see, it can be critical to have copyright infringement insurance coverage as a blogger, podcaster, columnist, or other content creator. It’s imperative that we know our rights to use something (or to NOT use something) and what we can do to protect yourself. Copyright infringement can carry a serious penalty, and insurance coverage is a good way to insure that you’re protected from hefty fines. Talk to you current insurance provider and copyright lawyer to find out what you need to do, and what you need to know, to get proper insurance for your needs.