Welcome to fmbb.net

Web Hosting - Email Issues When you build a web site, you often provide a means for users to communicate with you. One of the most common 'add-ons' to a web site is the addition of some kind of email access. Email is used to sign users up for newsletters, provide communication for administrative issues and a hundred other uses. But, as everyone sadly knows, email problems can occur. Virus infection is among the most common, though the situation is actually better today than in the past. Huge efforts, and some progress, has been made over the past 10 years to reduce the number and severity of virus attacks. Hackers haven't surrendered, far from it. But they're on the defensive like never before. Many of those viruses were (and are) spread through email, usually in the form of email attachments. That's the source of the now-common advice never to open an attachment from someone you don't know. Professionals will often extend that advice to suggest you never open an attachment that's unexpected, even if it's from someone you know. Well-meaning, but computer-challenged friends often accidentally forward virus infected emails. Spam has taken over the top spot for email annoyances. It's estimated by various different professional sources that 92-97% of all email sent today is spam. While the definition varies, spam is generally regarded as any unwanted commercial email sent by someone whom the recipient doesn't know or have a business relationship with. Spam clutters email inboxes, requires people to sift through to find valid messages, and often contains offensive messages in some form. But, it's a fact of life and isn't going away anytime soon. Even though laws are in place, thousands of spammers continue to risk fines or jail for the chance of making money from that small percentage who will open the unwanted email. Other forms of email problems are even more severe for many web site owners. When the mechanisms fail that they rely on to send and receive messages to and from their users, that's a problem. Dealing with those problems can range from sending an email or instant message to an administrator, to tracking down the right person to get your site removed from a blacklist. Email is the communications vehicle of choice for millions everyday. When the system burps, someone has to take time to do something about it. Often, that means relying on a person who is already overburdened with too many issues to resolve. So, besides pointing out some sad facts or complaining, what's the point? All of the above shows just one more area you should look at when selecting a web host or deciding whether to move to another. Just as with server or network administration, companies vary in their ability to deal with email-related issues. Some are responsive and super-competent. Others, are simply indifferent or worse. And many are in between. Email administration, like server maintenance or network management, is a professional specialty. Skill in one does not necessarily mean quality work in another. Finding a web hosting company and/or system that has few email problems, and solves them quickly when they occur, is an important task. Spend some time researching who provides superior support in email. You'll be happy you did.

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.

Web Hosting - The Internet and How It Works In one sense, detailing the statement in the title would require at least a book. In another sense, it can't be fully explained at all, since there's no central authority that designs or implements the highly distributed entity called The Internet. But the basics can certainly be outlined, simply and briefly. And it's in the interest of any novice web site owner to have some idea of how their tree fits into that gigantic forest, full of complex paths, that is called the Internet. The analogy to a forest is not far off. Every computer is a single plant, sometimes a little bush sometimes a mighty tree. A percentage, to be sure, are weeds we could do without. In networking terminology, the individual plants are called 'nodes' and each one has a domain name and IP address. Connecting those nodes are paths. The Internet, taken in total, is just the collection of all those plants and the pieces that allow for their interconnections - all the nodes and the paths between them. Servers and clients (desktop computers, laptops, PDAs, cell phones and more) make up the most visible parts of the Internet. They store information and programs that make the data accessible. But behind the scenes there are vitally important components - both hardware and software - that make the entire mesh possible and useful. Though there's no single central authority, database, or computer that creates the World Wide Web, it's nonetheless true that not all computers are equal. There is a hierarchy. That hierarchy starts with a tree with many branches: the domain system. Designators like .com, .net, .org, and so forth are familiar to everyone now. Those basic names are stored inside a relatively small number of specialized systems maintained by a few non-profit organizations. They form something called the TLD, the Top Level Domains. From there, company networks and others form what are called the Second Level Domains, such as Microsoft.com. That's further sub-divided into www.Microsoft.com which is, technically, a sub-domain but is sometimes mis-named 'a host' or a domain. A host is the name for one specific computer. That host name may or may not be, for example, 'www' and usually isn't. The domain is the name without the 'www' in front. Finally, at the bottom of the pyramid, are the individual hosts (usually servers) that provide actual information and the means to share it. Those hosts (along with other hardware and software that enable communication, such as routers) form a network. The set of all those networks taken together is the physical aspect of the Internet. There are less obvious aspects, too, that are essential. When you click on a URL (Uniform Resource Locator, such as http://www.microsoft.com) on a web page, your browser sends a request through the Internet to connect and get data. That request, and the data that is returned from the request, is divided up into packets (chunks of data wrapped in routing and control information). That's one of the reasons you will often see your web page getting painted on the screen one section at a time. When the packets take too long to get where they're supposed to go, that's a 'timeout'. Suppose you request a set of names that are stored in a database. Those names, let's suppose get stored in order. But the packets they get shoved into for delivery can arrive at your computer in any order. They're then reassembled and displayed. All those packets can be directed to the proper place because they're associated with a specified IP address, a numeric identifier that designates a host (a computer that 'hosts' data). But those numbers are hard to remember and work with, so names are layered on top, the so-called domain names we started out discussing. Imagine the postal system (the Internet). Each home (domain name) has an address (IP address). Those who live in them (programs) send and receive letters (packets). The letters contain news (database data, email messages, images) that's of interest to the residents. The Internet is very much the same.