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.

Ten Top Things That Make for a Great Employee If there is one thing that everyone can agree upon in the job market it is that great employees are hard to come by. Whether you are an employee yourself and you feel like you are always pulling the weight of the other people in the office or if you are a boss who is wondering how you can actually get some people on board who can do the job, you know that great employees are at a premium. But what exactly makes an employee great? These ten top things are guides to bosses looking for greatness in a new hire and for employees trying to get noticed in the workplace and be the kind of employee who has the potential to move up in the company chain. The first thing that makes an employee great is that they are always dependable. Great employees do the job they are supposed to do every time, and no one has to worry that they don’t deliver the goods. A great employee can be counted to always have their work done right, when it is supposed to be done – it is a forgone conclusion that they will, and no one else has to spend any time worrying about it. The second thing to look for in a great employee is that they are a team player. A great employee isn’t one who is constantly looking for attention or hogs the spotlight. Instead, a great employee works with everyone else to make sure that the things that need to get done do get done, for the good of the company. The third mark of employee greatness is that they know how to take direction. Great employees know how to take criticism, direction and advice gracefully and make it work for them when doing their job. Fourthly, a great employee can be trusted. They don’t spread office gossip and they don’t dish company dirt. Likewise, they always tell the truth to their employer, even if it lands them in hot water. The fifth sign of greatness in employees is linked to the fourth – a great employee always guards the confidential nature of their business dealings and protects everyone’s privacy. The sixth thing that makes an employee great is that they participate in the day to day life of the office. They don’t bow out of meetings or skip the office birthday celebrations. These things may not be a fun part of working life, and everyone involved knows that everyone else has some place they would rather be – but a great employee wouldn’t be any place else. In seventh place comes the fact that a great employee gets along with other employees. Every office has one person that is in everyone else’s business and talks to loud on the phone and generally stirs things up and gets under everyone’s skin. This kind of employee zaps office morale – a great employee is a good co-worker to everyone. The eighth thing a great employee has is good working skills. It may sound obvious, but a great employee has the abilities needed to do their job, and they constantly seek ways to improve, like going to training seminars or seeking further education. Great workers have great skills. The ninth thing that leads to employee greatness is tact and decorum. If there is a problem in the office, a great employee doesn’t make a scene in front of everyone else. A great employee will deal with such issues with privacy and diplomacy. Further, a great employee doesn’t tell tasteless, political or religious jokes, nor do they send emails that tell these kinds of jokes. Last but not least, a great employee has a great attitude. Bad attitudes bring everyone down. A great employee helps make work great for everyone else by having a good spirit about their job.

Web Hosting - Is a Dedicated Server Worth What You Pay? In reviewing web hosting plans, many web site owners are faced at some point with the decision of whether or not to pay for a dedicated server. A dedicated server is one which holds your site(s) exclusively. It's not shared with other sites. You then have the option to put one site or many on that piece of hardware. But the decision is never easy. There are multiple considerations to take into account, far beyond just the higher dollar outlay that inevitably accompanies a dedicated server option. Performance is (or should be) a prime consideration for the majority of site owners. Studies show that when a page doesn't load within about 10 seconds or less, almost everyone will give up and go elsewhere. The delay may be caused at any of a hundred different points in the chain between the server and the user. But often, it's the server itself. In any case, it's important to eliminate the server as a possible bottleneck, since it's one of the few points over which the site owner can exercise some control. That need for control extends further than just performance, however. Other aspects of the user experience can benefit or suffer from server behavior. Security is a prime example. With the continuing prevalence of spam and viruses, a server can easily get infected. Having only your site(s) on a single server makes that issue much easier to deal with. With fewer sites on a server, there is less likelihood of getting infected in the first place. Also, since you will place a higher value on security than many others, it's easier to keep a dedicated server clean and your site well protected. You can use best practices in security to fortify your site. Having other sites on the server that you don't control raises the odds that your efforts are for nothing. One way your efforts can get watered down is through IP address sharing. Less sophisticated hosting services will often assign a single IP address to a single server and multipe sites. That means your site is sharing the same IP address with other domains. That leaves you vulnerable in several ways. Virus or spam attacks may target a particular IP address. If you have the same one as another site, one that is more likely to attract hostile intentions, you suffer for and with someone else. In other cases an IP address range is assigned to the server, with each site receiving its own address from within that range. Though better than the one IP:server scenario, this still presents a vulnerability. Many attacks try a range of IP addresses, not just a single one. But even legitimate sources can give you trouble when you share an IP address or a range. If another site engages in behavior that gets it banned, you can suffer the same fate if they ban the address or range. If the miscreant that shares your server/IP address or range is himself a spammer for example, and gets blacklisted, you can inadvertently be banned along with him. Using a dedicated server can overcome that problem. There's a certain comfort level in knowing what is installed on the server you use, and knowing that you alone put it there. But a dedicated server option may require increased administration on your part. If you're not prepared to deal with that, you may have to pay still more to have your dedicated server managed by someone else. All these factors have to be weighed carefully when considering a dedicated server plan.