I will attempt to quickly teach you a bit about the Internet; if
you need more explanation, feel free to send me private email
and I'll do my best. Feel free to ignore the more detailed stuff
in parenthesis, and remember that Wikipedia can be your friend.
At 09:54 AM 6/10/2008, Kezzabear wrote:
>AAAAAAAAAAAAAAAAAARRRRRRRRRRRGGGGGGGGGGGGGGHHHHHHHHHHHHHHHHHH
>
>It comes and it goes ... *sigh*
Do you know what a router is, and what an IP address is?
If you don't, they're fairly simple at a high level. For
now, just imagine that your connection is divided into a
bunch of envelopes called packets that contain your precious
data inside, much like snail mail. You drop an packet/
envelope into the system, and routers/post offices forward
the packet/envelope to one that's closer to the destination,
until the destination is reached, or something bad happens
and the packet is dropped on the floor (and your computer
eventually tries again). Your computer, SIYE, and all the
routers in between all have IP (Internet Protocol) addresses,
and most of them are named fairly obvious things, see below.
Try the traceroute command. In Windows, at a command prompt
(in XP, it's in Accessories) type:
tracert www.siye.co.uk
Under UNIX, Linux and probably the Mac, it's traceroute instead
of tracert.
Here's what I got, and interpretations that start with three
tildes ("~~~"):
Tracing route to siye.co.uk [207.61.110.120]
~~~ www.siye.co.uk is an alias for siye.co.uk, and 207.61.110.120
is its IP address (much like your home post box address).
over a maximum of 30 hops:
~~~ The above states traceroute will try only so far, in case
there's something weird like a loop messing things up.
1 <1 ms 1 ms <1 ms 192.168.1.1
~~~ This is my home Internet connection's gateway. (IP addresses
like 192.168.x.x or 10.x.x.x are special and used for things
like your home network. My gateway router is a Network Address
Translation (NAT) box, those special addresses are "unroutable"
and not on the real Internet, the above address is from my
side, and adsl-65-65-224-26.dsl.spfdmo.swbell.net is the one
on the other side and is the IP address that's really on the
net right now.)
2 13 ms 13 ms 11 ms adsl-65-65-225-254.dsl.spfdmo.swbell.net [65.65.225.254]
3 14 ms 11 ms 13 ms dist2-vlan60.spfdmo.sbcglobal.net [151.164.88.163]
4 11 ms 11 ms 13 ms bb1-g1-3-0.spfdmo.sbcglobal.net [151.164.88.225]
~~~ OK, I live in the southwest part of the state of Missouri (MO),
USA, and Springfield, MO is the biggest city here, about 70 miles
away. The above is AT&T (formally Southwestern Bell Company, SBC)
sending my packets through an ADSL connection and routing them
through their Springfield facilities.
5 30 ms 30 ms 30 ms 151.164.189.80
~~~ This router has not been given a handy name, but I can go to
http://www.arin.net/index.shtml and cut and paste its IP address
(151.164.189.80) and see that it's owned by AT&T/Southwestern Bell
Internet Services. ARIN is the (North) American Registry for
Internet Numbers, if you're in another part of the world, you'll
be told to go to the right web site to find out who owns it.
6 29 ms 29 ms 30 ms asn577-bell-ca.eqchil.sbcglobal.net [151.164.250.242]
7 29 ms 29 ms 29 ms core2-chicago23_POS8-3.net.bell.ca [64.230.223.21]
~~~ The above is the first interesting thing here. Basically, in
some machine room in Chicago, AT&T (SBC) and Bell Canada exchange
packets. (If you want to read in detail, read the first backwards:
SBC Global at its "eq" exchange? in Chicago is connecting to Bell
Canada's ASN (Autonomous System Number, a fancy name for a bunch of
networks that are treated as one, with one ASN) 557. And the second
is Bell Canada, probably using a special reliable telephone network
connection abbreviated POS (Packet over SONET/SDH), connecting to
Chicago. core2 probably means this is the 2nd part of the core
(inner) network---no special meaning to #2, that's just how they
designed and evolved their network. All these technical and
geographic names for routers are designed to help the network
engineers know what is what (otherwise you'd be "in a maze of
twisty passages, all alike" :-)).
8 39 ms 41 ms 39 ms core3-toronto63_pos10-0-0.net.bell.ca [64.230.147.9]
9 43 ms 43 ms 43 ms core4-kitchener06_POS6-1-0.net.bell.ca [64.230.140.250]
~~~ OK, here my packets are being sent to Toronto and then
Kitchener, Canada. The latter is part of Regional Municipality
of Waterloo, Ontario, and the University of Waterloo is famous
and well respected for its Computer Science program. (I also
noted on Wikipedia that it "maintains the largest co-op program
in the world" and very interestingly, "UW has a long-standing
intellectual property policy that leaves ownership rights with
the inventor, rather than the university, which has helped create
many spin-off companies that maintain a good relationship with UW."
To an American, this is a radical concept: as a rule, neither our
public (like Waterloo) or private universities do this, although
the smarter ones share the wealth.)
Anyway, my point here is that the Waterloo region is a likely
good one for web hosting services in Canada.
10 41 ms 41 ms 43 ms 206.47.229.194
~~~ Owned by Bell Canada
11 * * * Request timed out.
~~~ Doesn't necessarily mean much, some routers ignore the
queries that traceroute sends out. But if you get a set
of lines like that, you know that's likely where your problem
is. Compare it to a successful traceroute you did previously
and saved away.
12 44 ms 47 ms 45 ms siye.co.uk [207.61.110.120]
~~~ OK, we're at SIYE, no problems here. You can safely
ignore the rest if you want to, or find out a little bit more
about "computer stalking" ^_^.
This is owned by Bell Canada and allocated to "Computer Partners"
(for a variety of technical and administrative reasons, many
IP addresses are owned by the network and allocated to their
customers on a temporary or semi-permanent basis; my ADSL IP
address 65.65.224.26 is very temporary, hours, days or weeks,
but not longer. Computer Partners will most likely keep theirs'
for the duration of their contract with Bell Canada. SIYE can
change web hosting providers since we know it by it's Domain
Name System (DNS) name "siye.co.uk", not "207.61.110.120".
Registered in the UK, provided in Canada, read (by me) in the
USA? No problem! :-).
Using "whois siye.co.uk" (generally not available on Windows
systems, you'll need UNIX/Linux/whatever), I can see that Computer
Partners (a totally generic name) is in this case compar.com,
which is indeed has a Waterloo real world address.
And I'm stunned by their cluefullness; they've got two DNS servers
with very different IP addresses. This means that if their own
system/connection goes down, siye.co.uk is still known by the rest
of the net (the other DNS server is maintained by Bell Canada it
would appear, and automatically picks up changes from the one
Computer Partners maintains), it'll just be unreachable. Almost
no one knows to do this.
This is *the very first thing* I check when evaluating a services
provider like a web hosting company. If they get this right,
then there's a good chance they get a lot else right (and it's
no accident the ISP that handles ancell-ent.com is one of those).
The one caveat I'd insert here is that I get the impression from
what I see and don't see that Bell Canada is the only way to get
to SIYE. This saves money in all sorts of ways (you don't need
additional connections or staff that understands this more
complicated way of doing things (e.g. BGP routing)), but like
everything it's a tradeoff, one that the wild and untamed Internet
lets you make.
ObHPFanfic: I was in the right mood and started reading Intromit's
Fate's Debt. It's cute and fun.
- Harold
Errr ... I should point out that while they have two very different
name servers listed, that doesn't mean they're both working. I've
forgotten a lot of my nslookup fu (which is obsolescent anyway), but
it doesn't look like the second server toroondcnszs04.srvr.bell.ca
is responding usefully to queries, nslookup just spits out the root
nameservers.
Someone more up to date might want to check this out (note also that
you can have many more DNS servers than the two listed by whois). If
one or more servers are bogus that can cause problems, and I have no
idea how the various client DNS programs or e.g. your broadband
gateway, which you will often go through, will handle them.
Right now I'm using opendns.com to avoid targeted attacks against
my DSL broadband gateway (a 2WIRE on AT&T's DSL service; this is
common enough that crackers have crafted special attacks...).
And here's a clue that might tie into your above observation: the
Time To Live (TTL) for www.siye.co.uk/siye.co.uk as reported from
the nameserver that's working (ns1.compar.com) just happens to be
one hour.... TTL is used for caching: when your client DNS
resolver looks up a name, it's supposed to keep it in its cache
for the TTL period, and after that look it up again. So if you
get bad data when you look up a name, it won't get automatically
flushed until the TTL period has passed.
More fun if Dino wants to wade into this, just after he got email
notification working again. Appropriately enough, the first one I
got was for the first chapter of his new story, which definitely
looks interesting. It's the first one I've read with the origin
of [that would be telling] covered, and that was convincing.
- Harold
Was about to submit the next Chapter of my story too.
-----Original Message-----
From: thecrack...@googlegroups.com
[mailto:thecrack...@googlegroups.com] On Behalf Of Miri
Sent: Monday, July 14, 2008 11:55 PM
To: TheCrackedMuggle
Subject: [TheCrackedMuggle] Re: Siye down?
Are the stories stored in the actual database or as text files?
How much space does the partition have?
Chris
-----Original Message-----
From: thecrack...@googlegroups.com
[mailto:thecrack...@googlegroups.com] On Behalf Of melkior
Sent: Tuesday, July 15, 2008 7:40 AM
To: TheCrackedMuggle
Subject: [TheCrackedMuggle] Re: Siye down?
It seems that they are working on it as the site has been up and down all
morning...
Chuck