Welcome to elreno.org

Web Hosting - Do It Yourself Administration, Things to Consider The choice of whether or not to try to administer your own web site brings with it a host, pun intended, of issues. For most web site owners, the primary focus is naturally on creating, maintaining and enhancing the site. That often is just part of managing an entire business, for which the web site is just the means to an end. That implies there will be little interest in or time left over for technical administration like database maintenance (tuning, space management, security, bug fixes), establishing and maintaining backups to ensure they're successful and usable, email administration, disk space management, applying operating system fixes for bugs and security, and other tasks. But cost is always a factor in any business. Paying for technical help can burden the budget of a new and struggling business. Consulting fees can range from a few dollars an hour to over $100. On the lower end, the poor skill level and quality of work will make it not worth even that small amount. On the higher end, you can quickly rack up expenses that will bust your business. Permanent employees are usually somewhere in the middle of that range when you add up salary, employment taxes and more. Often, server and/or web site administration can be paid for as part of the web hosting package. That cost is usually lower than independent contracting help, but those staff are usually tasked with maintaining dozens if not hundreds of servers and sites. They can, therefore, give very little individual attention to yours. Often, novice web site owners are intimidated by some of the technical requirements for server or site administration. But, as with anything, a little familiarity can show that the knowledge required is more modest than one might expect. Administration in many cases involves fairly elementary, and frequently repetitive, tasks. These can be learned easily. Using a test site or a free hosting service is a good way to practice and learn without risk or cost, other than time invested. Once that initial hurdle is jumped over, administration can be done quickly and some even find it interesting. It allows the site owner to exercise additional control over the total product, and there's satisfaction in being able to say 'I did that' even if you prefer not to do it forever. That real-life learning experience also allows the site owner to better judge any consultants or staff that are hired. It's much easier to judge if someone is providing you with an accurate assessment of a problem if you've solved it yourself. Any time-estimate they provide to fix it can also be better calculated if you've had to do it yourself. Every web site relies on a variety of factors, usually unseen, in order to continue to function properly. But the fact is that they misbehave from time to time. Deciding whether to tackle those problems yourself depends on your available time and skill set, and what it will require to get things back on track. In other words, it's a standard cost-benefit analysis that everyone has to undertake every day in life.

Web Hosting - When Changing Web Hosts Nearly everyone will want to change to a new web host at some point. It may involve just changing out old hardware for new. It usually means finding an entirely new web hosting company. When faced with that decision there are a number of issues to be considered. Swapping hardware and/or software is a fairly straightforward decision. There are two possible scenarios. Either you maintain your own hardware and software at a facility managed by others, or you are considering upgrading to newer (usually more expensive) systems maintained by others. In either case, it's simply a matter of estimating the cost and the short-term impact versus the long-term benefits. If the system(s) you currently use are short on capacity, sooner or later you'll be sufficiently motivated to make the change. Either the hardware will become unreliable or loaded to the point you'll be forced to migrate, or your needs will expand enough to justify the effort and expense of moving. Similar considerations apply to the scenario in which you rely on the web hosting company for everything, and want to find someone else to rely on. Regrettably, that's a very common situation. Many web hosting companies provide systems and staff that sooner or later fall below an acceptable level. Most people make the decision to change based on emotion. That's not entirely bad. Emotions incent you to take action. But you need to keep a cool head, too, in order to calculate your long-range self-interest. Bearing some minor inconveniences from time to time is usually worth the trade off. When it begins to affect your site to the point you're losing visitors, it's time to make a change. To get a more objective handle on when that point is reached, reach for some numbers. Maintain, or get from the hosting company, a factual report about availability and current usage. If the server is down so much, or so heavily loaded, that it drives your visitors away, it's time to take action. There are other less easily quantifiable but equally important factors, as well. You will at some point need to communicate with one or more persons who help maintain your site. Even if you do all your own server, database and web site maintenance, someone behind the scenes is helping to keep things running smoothly. That's called 'infrastructure'. If the road you drive on has potholes, it's not enough that you can fix your own car. In terms of network bandwidth and availability, server capacity, disk space, security and a whole array of other aspects, the web hosting company has to have competent people who care (and are allowed) to do the job well. When the company's people fall down - because of incompetence, lack of resources or absence of a culture of excellence - or for any other reason - your web site suffers. This issue more than any other is what drives people to seek another web hosting company. Even if you choose well at the outset, things can change. Management changes, staff changes and companies are taken over by other companies. Sometimes, it isn't simply a matter of swapping out an unreliable piece of hardware or software. When it's time to swap out people, you look for the same aspect: doing the job required.

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: 209.131.36.158 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.