| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 50891 | 2004-11-04 22:43:00 | site access | dagon (1357) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 288039 | 2004-11-04 23:43:00 | Give Brian Moon a phone call | Rob99 (151) | ||
| 288040 | 2004-11-05 00:01:00 | try phorum.org rather than http: . :D The "www" does not always exist in web site names. It's only part of a name when it does exist. If it doesn't exist, putting it in will guarantee a "non exist" error.:D Only a "fully qualified domain name" registered with the name servers is any use. You don't just arbitrarily add "www" to a site's name "because it is a web server".:;-) |
Graham L (2) | ||
| 288041 | 2004-11-05 00:09:00 | > try http://phorum.org rather than > http://www.phorum.org . :D The "www" does not always > exist in web site names. It's only part of a name > when it does exist. If it doesn't exist, putting it > in will guarantee a "non exist" error.:D That's what he had been trying. > Only a "fully qualified domain name" registered with > the name servers is any use. You don't just > arbitrarily add "www" to a site's name "because it is > a web server".:;-) I don't think so Tim. A web-server should respond to www.domainname.xx.xx - as that is the service it is providing and the standard naming convention. Just like pop3.domainname.xx.xx etc - it is actually the basedomain that should not respond by default when addressing a website - some places do it but it is not a requirement and certainly not standard. |
whtafo (156) | ||
| 288042 | 2004-11-05 00:11:00 | yeah new that but it makes no difference in this case - but thanks. | dagon (1357) | ||
| 288043 | 2004-11-05 00:16:00 | dig +trace @ns1 . cisco . com phorum . org ; <<>> DiG 9 . 2 . 4rc6 <<>> +trace @ns1 . cisco . com phorum . org ;; global options: printcmd . 108079 IN NS I . ROOT-SERVERS . NET . . 108079 IN NS J . ROOT-SERVERS . NET . . 108079 IN NS K . ROOT-SERVERS . NET . . 108079 IN NS L . ROOT-SERVERS . NET . . 108079 IN NS M . ROOT-SERVERS . NET . . 108079 IN NS A . ROOT-SERVERS . NET . . 108079 IN NS B . ROOT-SERVERS . NET . . 108079 IN NS C . ROOT-SERVERS . NET . . 108079 IN NS D . ROOT-SERVERS . NET . . 108079 IN NS E . ROOT-SERVERS . NET . . 108079 IN NS F . ROOT-SERVERS . NET . . 108079 IN NS G . ROOT-SERVERS . NET . . 108079 IN NS H . ROOT-SERVERS . NET . ;; Received 260 bytes from 128 . 107 . 241 . 185#53(ns1 . cisco . com) in 76 ms org . 172800 IN NS TLD2 . ULTRADNS . NET . org . 172800 IN NS TLD1 . ULTRADNS . NET . ;; Received 110 bytes from 192 . 36 . 148 . 17#53(I . ROOT-SERVERS . NET) in 42 ms PHORUM . ORG . 172800 IN NS NS2 . OVERSTABLE . COM . PHORUM . ORG . 172800 IN NS NS1 . OVERSTABLE . COM . ;; Received 88 bytes from 204 . 74 . 113 . 1#53(TLD2 . ULTRADNS . NET) in 36 ms phorum . org . 86400 IN A 207 . 111 . 175 . 100 phorum . org . 259200 IN NS ns1 . overstable . com . phorum . org . 259200 IN NS ns2 . overstable . com . ;; Received 126 bytes from 207 . 111 . 175 . 101#53(NS2 . OVERSTABLE . COM) in 91 ms bettter from my us web host but not much use to me in NZ, could just grag it though the webserver but why should i have to . odd that its unavalable in nz |
dagon (1357) | ||
| 288044 | 2004-11-05 00:23:00 | > bettter from my us web host but not much use to me in > NZ, could just grag it though the webserver but why > should i have to. odd that its unavalable in nz Get used to it unfortunately. More and more sites are restricting themselves off to their own country only - George Bush did it, some popular TV stations are starting to do it as well. You could try contacting the site operator and request they remove the restrictions but I wouldn't hold your breath. |
whtafo (156) | ||
| 288045 | 2004-11-05 00:30:00 | i did get in touch and they said it was nothing to do with them. | dagon (1357) | ||
| 288046 | 2004-11-05 00:30:00 | A web server will respond to "www.domainname.xx.xx" only if exactly that name is registered in the DNS system. If the server has the registered name "mywebserver.domain.xx.xx" it won't respond to "www.mywebserver.domain.xx". In fact, the server does not respond to anyname ... it can only respond to its IP address, which is a 32 bit (or 128 bit) number. That number is provided by the DNS system, which provide answers only to names which are registered. The service a web server is providing is the http: protocol, indicated by the http:// component of the URL. I belive that some browsers (I know Netscape 3 did) will prefix "www" a site address after receiving an error message. This will make it appear (to the user) as if "mywebserver.domain.xx.xx" and "www.mywebserver.domain.xx.xx" are equivalent. They are not, unless they are made to be so by registering both names and defining them to return the same IP address. |
Graham L (2) | ||
| 288047 | 2004-11-05 02:25:00 | Maybe it was a security issue and Bush put iton the banned list of servers that could not be contacted outside of the USA. | Big John (551) | ||
| 1 2 | |||||