Ručali smo meso,
Glodali smo kosti dobrih životinja,
Mi imamo snage,
Mi imamo snage za još dan.
EKV, Kao da je bilo nekad

Uskom cestom uz Savu, klizio je auto vođen kumovim sigurnim rukama. Po ušima me miluje Leb i sol. U trenutku se osjećam tako spokojno. Sve je nestalo. Zavaljena na zadnjem sjedištu prepuštam se opojnom dimu. Kroz prozor pratim kako promiče magloviti krležijanski krajolik.
Slušam priču o treš hororcu. Kao, svemirska bića skuže da im je ljudski mozak prava delikatesa. Pa žele na zemlji otvoriti fast fud lance sa ljudskim mozgovima. Kao delikatesom.
Zamisli, stvarno. Da nas uzgajaju za hranu. Na farmama. Zbog mozga. Smijeh. Pa, mi ljudi smo tako ... inteligentni. I superiorni. Nemoguće.
A opet, i nije tako nemoguće. Ljudi to, bez grižnje savjesti, rade životinjama. Uzgajaju ih, ubijaju i jedu. Na trenutak se zamislim.
A onda, stižem do kuće. Gurnem glavu u frižider i gledam. Analiziram. Frižider mi je pun ostataka ubijenih životinja! Što sad? Pomirena sa sudbinom slažem veeeliki sendvič. Sa šunkom.
Masnih prstiju, odsurfam na stranice prijatelja životinja i punih usta, udružim se u udrugu istih.

Sjedimo na stepenicama.
U sumrak.
Razgovor i dim.
O prošlosti. O budućnosti.
Stepenice silaze do rijeke.
A dolje su čamci.
Čamci se zibaju.
Na vodi.
S druge strane rijeke trepere svjetla.
Na prozorima.
Razmišljam.
Što je iza prozora?

HeKata

The Domain Name System or Service (DNS) is a process that maps hostnames (how humans address servers) to IP addresses (how computers address servers).When you visted www.dyndns.org, your computer resolved that hostname as 63.208.196.100. This translation happens every time you access a website, FTP server, or your e-mail.

Here is an example of how DNS works when accessing a website. There are three parts necessary for someone to access a remote service on a server: domain registration, DNS service, and the actual service such as a website:

Domain registration
The virtual real estate - Purchasing a domain gives you a lease to a domain name from a domain registry like .com, .net, or .org. The domain registrar allows you to specify nameservers for that domain.
DNS
The glue - When someone types in a domain name like 'dyndns.com', a process called the domain name system (DNS) works to turn that name into a number called an IP address. Only with the number can you access a website.
Service (eg. web site, email, FTP)
The content - After the DNS is resolved, the client will access the service at the given IP address and return a webpage in this case.

DNS is a required "glue" for any Internet application or service where you use a hostname or domain name. DynDNS provides domain registration and DNS service in addition to mail services and network monitoring.

There seems to be a lot of confusion on the Internet at large as to how DNS works. This is a quick (somewhat technical) run-down of how a DNS query works. Most of these servers/hostnames do exist, but these delegations aren't necessarily valid, and we know some of this is short-circuited in some configurations. This is explained the longest way possible to convey the most information possible.

So, you want to resolve the IP address of www.dyndns.org. How does your computer talk to ours? Well, that name really doesn't mean anything in and of itself; traffic on the Internet is routed using IP Addresses, which are sets of four numbers, each between 1 and 255, something like 63.208.196.100. DNS simply provides a mapping from www.dyndns.org-style names to 63.208.196.100-style IP addresses. Pretty simple so far, right?

Well, now it starts getting more complex. You're sitting at your computer, and you try to access www.dyndns.org. What happens first? Your computer probably asks your ISP's nameserver, which was configured when you dialed in or got your DHCP lease. It will be doing the rest of the work for you, because it operates recursively.

How does your ISP's nameserver find the answer for you? We'll assume that it doesn't have any information cached - that is, stored from things it's already looked up in the past. Caching can short-circuit some of this process, but we want to go through the whole process to understand it better. At each stage of this process, your ISP's nameserver will be asking for information about www.dyndns.org. Unlike your first query, though, none of these servers will be recursive, so they'll only give a more limited set of information based on what they already know. First, the server will send a query to the root-servers. These are a group of very high-powered servers that know about all the Top Level Domains, such as com, net, org, and all the country domains. So, your ISP's server will ask one of them, say, e.root-servers.net (they're named a through m) what it knows about www.dyndns.org. It'll respond that it only knows one bit of information - org is served by a bunch of other nameservers, the GTLD-servers.

This is a referral; the root server your ISP's server queried will give you the names and IP addresses of the GTLD servers for .org, including, for example, tld1.ultradns.net. Your ISP's server will then follow the delegation and ask one of those servers what it knows about www.dyndns.org. The answer will come back that this server knows a little bit more - dyndns.org is served by ns1.dyndns.org, ns2.dyndns.org, ns3.dyndns.org, ns4.dyndns.org and ns5.dyndns.org.

Your ISP's nameserver will continue diligently following the delegation, and ask ns.dyndns.org what it knows about www.dyndns.org. Lo and behold, it gives you an actual IP address (or an authoritative "that host doesn't exist" answer), which your ISP's nameserver will then return to you, the client. You can then use that IP address to talk to our server!

At each step of this process, your ISP's nameserver will be caching the answers it gets - when you ask it for members.dyndns.org, it will be smart enough to go back to ns.dyndns.org, the server that it knows is authoritative for dyndns.org hostnames. That information is cached for a length of time specified by the TTL of the DNS records, which is part of the information it got in reply to every query it was making earlier in the process.

Article 1
All human beings are born free and equal in dignity and rights. They are endowed with reason and conscience and should act towards one another in a spirit of brotherhood.

Article 2
Everyone is entitled to all the rights and freedoms set forth in this Declaration, without distinction of any kind, such as race, colour, sex, language, religion, political or other opinion, national or social origin, property, birth or other status.

Furthermore, no distinction shall be made on the basis of the political, jurisdictional or international status of the country or territory to which a person belongs, whether it be independent, trust, non-self-governing or under any other limitation of sovereignty.

Read all...
Croatian Version...

You can host your own web site at home, and I'll tell you exactly how! But it might not save you much money, and it definitely won't save you time. So give it serious thought before you proceed... unless your goal is simply to learn about the technology and have fun!

The best reason to host your web site at home is to learn how it all works. For more information about the pros and cons, see should I host my own web site?

Warning: running a server of any kind at home is a security risk. Security problems are sometimes found in server software, and these can be exploited to gain access to or damage your files. Your computer must be kept absolutely up to date with Windows Update or the equivalent for your operating system if you intend to run a web server on it. If you choose to run Apache instead of Internet Information Server, you'll need to keep your version of Apache absolutely up to date too. This doesn't eliminate the risk -- it only minimizes it. You run a server at home entirely at your own risk. If you do choose to run a server at home, I recommend finding an old PC on the curb and setting it up as your home server, reducing the danger to your own computer.
Procedures for other operating systems are similar, and most of these steps actually involve your router, so this article should still be helpful to non-Windows users.

Here are the steps to follow to set up a web site hosted entirely on your own Windows PC. First I'll present the general steps, then I'll break down the details for you:

1. Make sure you have cable modem, DSL or another high-speed connection. A dialup telephone modem is NOT good enough.

2. Get a DNS hostname for your home Internet connection.

3. Get a static local IP address for your computer within your home network.

4. Configure your router to correctly forward connections on port 80 (the HTTP port) to your web server. If your ISP blocks port 80, choose an alternative port number and forward that (or get a better ISP that welcomes web sites at home, like Speakeasy.Net).

5. Configure Windows Firewall to allow your web server to communicate on port 80.

6. Get Apache, a free, high-quality web server program. If you have Windows XP Professional, you also have the option of Microsoft Internet Information Server (IIS), which comes standard with Windows XP Professional. But that option only allows you to host one site. I recommend Apache.

7. Test your web server from your own computer.

8. Replace the default home page with your own web page. Now the site is your own!

9. Test your web server from a computer that is NOT on your home network to make sure you followed all of the steps correctly.
"I followed all the steps and I get my router's login page instead of my home page!"
You are trying to access your web site by name from behind your router (from one of your own PCs). With many routers, this does not work because the router automatically assumes any web connection to itself from inside your network is an attempt to log into the router's configuration interface. Test from outside your own network or have a friend do that for you. If you can access your home-hosted web site from someone else's computer, you don't have a problem. If you want to access your site from a computer behind your router, you'll have to access it at its static local IP address instead of by name.
And that's it! Now I'll present detailed information about each step.

Step One: Broadband

Get cable modem (from the cable company) or DSL (from the phone company and various other companies). If you can't do that, you'll have to host your web site in some other way. to grapple with video and audio files anyway. You don't necessarily have to go with your phone company's DSL offering -- Check out broadbandreports.com for independent reviews of cable modem and DSL companies. Upload speed, not download speed, is the most important feature for hosting web sites at home.
"How fast will my home-based web site be?"
The main limitation will be your upload speed (uplink speed). Most DSL or cable modem connections have an upload speed between 128kbps (128,000 bits per second) and 384kbps (384,000 bits per second).

So how long does it take to load your home page? Add up the size of your home page (in bytes), the sizes of all of the images on that page, and the size of any Flash movies (.swf files) or CSS style sheets (.css files) referenced by that page. Now multiply by 8 and you'll know how many bits make up your home page. Divide that by your upload speed and you'll have a rough idea how long it takes to load your home page under ideal conditions. There will also be latency delays slowing things down, and multiple users will of course slow things down and make it take longer. There is no fixed limit on the number of users who can access your home-based web site at the same time - things just slow down.

For more information, see my article how fast is my web site?

Step Two: Dynamic or Static DNS

Other people can't talk to your web site if they don't know the address... and if you have a typical cable modem or DSL connection, your address changes often. You can solve this problem by using a dynamic DNS service. Even if your IP address doesn't change, you still need someone to host a DNS server for you, unless you are willing to put up with giving users a URL that begins with a string of numbers. This is a common requirement both for hosting web sites at home and for hosting torrents, so I've written a separate article explaining how to get a hostname for your computer at home.

Step Three: A Static Local IP Address

If you have a router... and you do, if you have WiFi (wireless access) or more than one computer... then your computer receives a new local address on your home network, or Intranet, every time it is powered on. But to forward web browser connections to your computer, you need an unchanging address to forward those connections to. This is also a shared requirement both for hosting web sites at home and for hosting torrents, so I've written a separate article explaining how to give your computer a static local IP address.

Step Four: Forwarding Port 80

If you don't have a router (and you know by now, if you have been following these steps...) then you can skip this step and move on to the next. IF you have WiFi, or more than one computer, you definitely have a router and must not skip this step.

Now that you have chosen a static local IP for your computer, you're ready to configure the router to forward web traffic to your computer.

Again, this step is needed both for web hosting at home and for BitTorrent hosting. So, once again, there is a separate article explaining how to forward ports from the Internet to your computer via your router. Just follow the steps in that article to forward port 80.

Step Five: Allowing Web Traffic Through The Firewall

More firewall issues? Didn't we already do this? Only in part. Yes, your router serves as a firewall, but your computer also has a built-in firewall. You'll need to configure that firewall to allow traffic through on port 80 to reach your web server software. This step is also common to both web hosting and torrent hosting... so check out my article explaining how to allow traffic on specific ports through your computer's firewall.

Step Six: Get Apache Or Internet Information Server

Mac and Linux users: you already have Apache! MacOS X users should read Kevin Hemenway's great article on onlamp.com. Linux users: install the Apache packages and look in /var/www/html or a similar location for your web site folder.
Apache is the most popular web server in the world, with nearly 70% of all web sites running Apache as of January 2006, according to the netcraft web server survey. Why is it so popular? Because it's free, open-source, high-quality software. And you can run it on your Windows box at home!

If you have Windows XP Professional, you can also run Microsoft Internet Information Server. It comes free in the box... but only with XP Professional (and high-end server versions of Windows). If you have XP Home, or an older version of Windows, go with Apache - and consider upgrading to at least XP Home for better network performance.

I'll cover Apache first. Then I'll look at Internet Information Server, which is also excellent and is available if you have Windows XP Professional or a high-end server version of Windows. It will only host one site per computer on XP Professional, though.
Windows 98 and Me users can use Microsoft's "Personal Web Server." However, this software went away with the release of XP Home, and it's not a popular choice. Since you can run Apache for free - the world's most popular web server, for businesses and individuals alike - I don't recommend suffering with PWS.

Apache Quick-Start Guide

Although Apache was born in the Unix/Linux world, it runs great on Windows too. In general, the newer your Windows, the easier it is to install Apache. Those with older versions of Windows, even Windows 95, can still run Apache but will have to jump through a few extra hoops. For complete information, check out the Apache Foundation's Microsoft Windows Apache installation tutorial. Since that article is a little old, you'll just have to bear in mind that instructions for Windows NT or 2000 also apply to Windows XP.
The following quick-start guide applies to Windows XP, but users of older versions of Windows can run Apache too... if they follow the extra steps spelled out in the Apache Foundation's Using Apache with Microsoft Windows tutorial to prepare their older computers to handle modern software installation and networking.

Upgrading to Windows XP Service Pack 2

Microsoft has fixed problems in Windows XP that create issues for Apache. Use Windows Update to upgrade your Windows XP system to service pack 2. You have probably already done this. If not, you need to do it in any case to fix many important security problems that have nothing to do with Apache!

Not sure if you have service pack 2? Do this: click on "Start," right-click on "My Computer," select "Properties" and look at the information presented under "System." You should see "Service Pack 2." If not, visit Microsoft's Windows Update site, using Interet Explorer, not Firefox... just this once! The Windows Update site uses special Active X controls to update your computer. Normally I don't encourage the use of Active X, but for upgrading Microsoft's own operating system from Microsoft's own web site using Microsoft's own browser, it's OK!

Downloading Apache

Visit the Apache HTTP Server Project home page. In the column at left, locate "Download!" and click on "from a mirror." The download page will appear. Scroll down until you locate the link to download the "Win32 Binary (MSI Installer)" distribution of Apache, not the "Win32 Source." That's raw source code for programmers - probably not what you want!

Click on the link for the "Win32 Binary (MSI Installer)" and wait for your browser to save the file to disk.

Installing Apache

Once the download is complete, you're ready to install the software. Double-click on the file you just downloaded on your desktop (for Firefox) or in your downloads folder (for Internet Explorer) to launch the installation program. The "Installation Wizard" window will appear.

First you'll see the "Welcome to the Installation Wizard" page. Click "Next" to continue.

Next, you'll see the Apache license agreement. The Apache license allows you to share the software freely, including the source code. Select "I accept the terms in the license agreement" and click "Next."

The "Read This First" page appears. Currently this page doesn't offer much specific information for Windows users of Apache. Click "Next."

The "Server Information" page should now appear. Be sure to enter the correct information:

1. For "Network Domain," if you registered a hostname such as myname.is-a-geek.com with DynDNS, enter is-a-geek.com.

2. For "Server Name," enter your full hostname, such as myname.is-a-geek.com.

3. For "Administrator's Email Address," enter a real email address for you that actually works. Users will see this when things go wrong. Bear in mind that spammers might discover this address, so use an address that is already publicly known if possible.

4. For "Install Apache HTTP Server 2.0 programs and shortcuts for..." select "for All Users, on Port 80, as a Service." This ensures that the software is always running, no matter who is sitting down at your computer. And a web site that is not always running is not very useful! So pick this option and click "Next."

The "Setup Type" page appears next. Select "Typical" and click "Next" to move on.

You'll see the "Destination Folder" page. By default, Apache installs in the folder C:Program FilesApache Group, creating a sub-folder called C:Program FilesApache Grouphtdocs to keep your web pages in. These are good choices, so click "Next." Don't click "Change..." unless you know exactly what you're doing.

Finally, the "Ready to Install the Program" page appears. Click "Install" to kick off the installation process. The Apache server software will be copied into place and the Apache service will start up in the background. Along the way, a few Windows Command Prompt windows will flash up briefly. This is normal and you should let these windows do their thing and go away on their own!
If you do receive error messages, the most frequent cause is that Internet Information Server or another web server is already installed and "listening" on port 80, the standard HTTP port. Disable the other web server software and reinstall Apache.

The "Installation Wizard Completed" page should appear. Congratulations, you have a web server! Click on "Finish" to complete the process.

Internet Information Server Quick-Start Guide
You need either Apache or Internet Information Server (IIS). You do not want both.
Microsoft's Internet Information Server is a solid choice, and it is included free with Windows XP Professional. If you don't have XP Professional, or one of the server-oriented versions of Windows like Windows Server 2003, then IIS is not an option for you.

Installing Internet Information Server

1. Make sure you have Windows XP Professional! Click "Start," then right-click "My Computer." Choose "Properties" from the menu that appears. The "General" tab will appear. Under "System:" you should see "Microsoft Windows XP Professional." If you see Windows XP Home, Windows ME, Windows 98 or Windows 95, you will not be able to use IIS. Follow the Apache Quick-Start Guide instead.

2. We're ready to install the IIS software. Select "Start," then "Control Panel," then "Add/Remove Programs." Select "Add/Remove Windows Components" from the left-hand column.

A list of available Windows features appears. Check the box for "Internet Information Services (IIS)" and click "Next." If prompted, insert your Windows XP installation CD.

That's all it takes! Installing IIS is very simple because it is a standard component of Windows XP Professional.

Step Seven: Test Your Web Site From Your Own Computer

Is the web site working? Let's find out! The first test is to access your site from your own computer. On the same computer that is running the web server software, access the URL http://localhost/. You should see an example home page provided with your Apache or IIS web server software. If not, review the appropriate quick start guide above and figure out which step you skipped! If you received errors during installation, you need to resolve them before your web site will work.

Step Eight: Make Your Own Home Page

You have a web server, but right now the "content" on the site is just the default home page that came with the server software. Time to fix that!

All you have to do is move your own web pages to the appropriate folder. If you followed the Apache quick-start guide, your web pages belong in this folder:

C:Program FilesApache Grouphtdocs

If you followed the IIS quick-start guide, your web pages belong here:

C:Inetpubwwwroot

First, remove the files that are already in those folders. It's not smart to leave "default" files lying around. What if a security problem was found with one of these common files? Then your web site would be vulnerable.

Next, copy your own web pages and images into the folder. The "home page" of your site should be called index.html (not index.htm). Both Apache and IIS are smart enough to know that when a user visits http://yourname.is-a-geek.com/, they should act as if the user asked for http://yourname.is-a-geek.com/index.html and do the right thing.

For more information about making web pages and graphics, see how do I set up a web site?

Step Nine: Test Your Web Site From The Outside World

We did a lot of work here to give our computer a hostname on the Internet and forward web traffic through the router and firewall. Did we do it right? Only one way to be sure! Access your web site from a computer that is not on your home Internet connection, or have a friend try it. For example, if you registered the name myname.is-a-geek.com with DynDNS, your web site's address is http://myname.is-a-geek.com/. Try that address from a computer outside your home and see what happens!

If it works... great! If not, you probably made a mistake in dynamic DNS, port forwarding, firewall configuration or local static IP configuration.
"I followed all the steps and I get my router's login page instead of my home page!"
You are probably trying to access your web site by name from behind your router (from one of your own PCs). With many routers, this does not work because the router automatically assumes any web connection to itself from inside your network is an attempt to log into the router's configuration interface. Test from outside your own network or have a friend do that for you. If you can access your home-hosted web site from someone else's computer, you don't have a problem. If you want to access your site from a computer behind your router, you'll have to access it at its static local IP address instead of by name.

Another possible cause of this problem: you may have turned on your router's "remote router access" feature by mistake. People turn this on by accident because they think it has something to do with hosting a web site at home. It doesn't. Turn it off, it is dangerous! You don't want other people accessing your router and changing configuration settings.
Congratulations! You have your own web site on the Internet, hosted entirely in your own home. Just remember: your computer must remain on, and connected to the Internet, all the time. Without a web server, there's no web site. That's why, if you choose to host at home, I recommend picking up an older computer off the curb, dusting it off, popping in at least 128MB of RAM and firing it up as a web server. Your own PC doesn't wear out, and if security problems are found in the web server, they are more likely to be confined to the less important computer.

To host a web site at home, or host BitTorrent downloads at home, you need a way for others to find your computer on the Internet.

Right now, your computer at home -- or, more likely, your connection sharing device, such as a wireless router -- probably has a dynamic IP address. That means that other users can only refer to your computer by a cryptic address that doesn't mean much to human beings, such as 10.250.17.234. And if your IP address is dynamic, it changes every time you reconnect to your DSL or cable modem provider.

Even if your IP address is static, you still need a way for users to access your site by name, instead of by number... unless you're willing to put up with a URL like http://10.250.17.234/. And you might change ISPs. So I recommend following this article's recommendations anyway. If a URL like that doesn't bother you, and you're sure you won't change ISPs and that you have a static IP address, You may skip this step. If you don't know which you have, you probably have a dynamic IP address.

So how can we give out a reliable address to folks who want to connect to our web site or BitTorrent tracker... for free? Easily: we'll use a dynamic DNS service, such as DynDNS. DynDNS offers free dynamic and static DNS services.

I use DynDNS as an example here, but you should also consider similar services offered by www.no-ip.com.

Visit the DynDNS site, or that of a similar free DNS service, and set up a dynamic IP DNS account for yourself. DynDNS offers DNS subdomain names in several domains with rather entertaining names. For instance, you might pick exampleguy.is-a-geek.com.
What if you want to use your own domain name, instead of is-a-geek.com or another domain offered by DynDNS? In a nutshell: it's tougher, and it's usually not quite free, but you can do it! For the sake of readability, I've separated my answer to that question into a separate article. Check out How do I host a real domain name at home? for complete details.
You have a dynamic DNS account now... but so far, you're still stuck logging in to DynDNS every time your IP address changes! How can you fix that? By installing the DynDNS Updater software, which stays resident on your computer and automatically updates your IP address in the DNS records, so that yourname.is-a-geek.com follows you everywhere you go. Even if you change from cable modem to DSL or vice versa, your dynamic DNS will still be updated to point to the right place. Neat, huh?

You can get the DNS updating software from the DynDNS Update Clients page. Installation is a snap, with just two confusing pages in the setup wizard: "Hostname Group" and "Hostname Information."

If you have just one hostname, it's hard to see why either of these is useful. Fortunately, all you need to do on the "Hostname Group" screen is make up a name for your "group" of hostnames. exampleguy will do fine. And when you reach the "Hostname Information" screen, just be sure to check the box next to your one and only hostname before clicking "Next." Also be sure to enable automatic update -- that's the whole point!

In my tests the Dynamic Update software showed an IP address only valid on my local network in a little popup "tooltip" window -- but my "real" public IP address was set correctly on the dyndns server. So don't panic.

Got a Mac or a Linux system? You can still have automatic DynDNS updates! Try the "third party clients" link at the bottom of the DynDNS Update Clients page.

Now you have your very own hostname on the Internet... for free! For most people, the next step is to assign a static local IP address to your computer so that you have a fixed address on your home network to forward web or BitTorrent traffic to.