The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
Large sites that control their own DNS pool can even direct *.something.tld to their webserver.. BIND and DNS is fun. I love understanding how the 'net works..
I'm quite interested in learning more about address resolution itself (ethernet theory, ip address -> route translation, etc). Anyone got any links to good sites / documentation past what google throws up?
WWW shouldn't really be there. Actually, I don't reall know why it is. If you have the domain "foo.com", THAT is the address, with the correct protocol. EG, if I was web browsing, I would be using HTTP and the address would be http://foo.com/ . You should also have the port as well (http://foo.com:80/), but that's implied. If you put a "www" before it, it becomes a subdomain and is technically a different address. http://ukdiscussions.reserve.co.uk/ is a subdomain. Usually the www is just ignored though. So, if you put a www in front of your domain, which is actually a subdomain, it's a different addres and therefore won't work.
also can someone tell me how to route my urls, e.g. if someone trys to log onto um, ukclansgs.netfirms (which is my domain) how do I route it to clansgs.netfirms.
hhmm, thanks for you help again.
I doubt this is what you want, because hardly anyone does. Just a thought.
What is/will be the address of the site?