Successful? Which ISP are you with?

[eFestivals]

Do you understand the concept of DSN servers and how they work?

yep - it's simply a search that looks up an ip address in a database.

There's sod all complicated about that from the perspective of a user DNS lookup.

[eFestivals]

Research shows Plusnet customers to be most paranoid

Fantastic.

[posthuman]

A point to consider:

If people were constantly hammering glastonbury.seetickets.com, is it possible that *their own* ISP was blocking them (as opposed to See), because their ISP thought that there was a DDoS attack originating from their PC?

[pie_and_a_pint]

That bloody woman can shove her "network is very busy, you have not been charged for this call" message up her chuffing arse

[rischbrit]

virgin 100mb line, I think having a fast connection helped as it meant I had no problems fully rereshing the page every couple of seconds.

[marketsqhero]

Ok as simple as it gets:

Your browser talks to your router, your router has a DNS server address that is defaulted to a DNS cluster owned by your ISP.

http://glastonbury.seetickets.com

Means absolutely nothing until that name has been resolved by the DNS server owner by your ISP. It's them routed by your ISP to the correct IP of the Seetickets load balancer.

See how many references to "your ISP" are in there? It totally makes a difference as to how hammered your ISP DNS servers are because that happens well before you hit Seetickets.

The edit the hosts file trick works because you resolve the name to the IP locally without using the DNS server.

Overloaded DNS owned by your ISP means you can't resolve the address and THAT is a bottleneck before anything else happens.

Also doing a Trace Route to the name will show you how many hops it needs to go through before hitting the See servers. Bad routing could mean extra hops and slower response.

[Spacey]

Ok as simple as it gets:

Your browser talks to your router, your router has a DNS server address that is defaulted to a DNS cluster owned by your ISP.

http://glastonbury.seetickets.com

Means absolutely nothing until that name has been resolved by the DNS server owner by your ISP. It's them routed by your ISP to the correct IP of the Seetickets load balancer.

See how many references to "your ISP" are in there? It totally makes a difference as to how hammered your ISP DNS servers are because that happens well before you hit Seetickets.

The edit the hosts file trick works because you resolve the name to the IP locally without using the DNS server.

Overloaded DNS owned by your ISP means you can't resolve the address and THAT is a bottleneck before anything else happens.

Also doing a Trace Route to the name will show you how many hops it needs to go through before hitting the See servers. Bad routing could mean extra hops and slower response.

[Spacey]

I tried changing host file and it made no difference. So not guaranteed. Friend got my ticket for me. I didn't see booking page

[marketsqhero]

I tried changing host file and it made no difference. So not guaranteed. Friend got my ticket for me. I didn't see booking page

[eFestivals]

The edit the hosts file trick works because you resolve the name to the IP locally without using the DNS server.

Overloaded DNS owned by your ISP means you can't resolve the address

now you're just showing that you don't understand how DNS works.

The hosts edit works for a different reason to that.

While you do need a dns lookup, the lookup is rarely made for every page request (tho it can be).

But given that I was using two IPs here `which use the same DNS server and one got as far as the payment page while the other (much more tried) PCs got no page at all, it's defo fuck all to do with DNS lookups.

Edited October 6, 2013 by eFestivals

[eFestivals]

Also doing a Trace Route to the name will show you how many hops it needs to go through before hitting the See servers. Bad routing could mean extra hops and slower response.

but which will make no difference to whether you get a page or not back from a responsive server or no page back from a non-responsive server.

The only difference it makes it to the timing of the exact moment your data packet makes its page request.

There's nowt more dangerous than a man with just a bit of knowledge.

[mikeb]

I don't think it is, is it?

But it does run over the BT network, as does Sky Broadband and (nearly?) everything else that uses the normal phone lines.

Edited October 6, 2013 by mikeb

[dan05delaney]

Most useless Poll ever... surely this is just showing the most popular ISP's site users use...

[marketsqhero]

A) You still need a response back from the DNS before it's locally cached. Saturated DNS will effect how long it takes to get a valid IP, and yes, that is exactly what a local hosts file is for.

B ) I never said it effects whether you get a page back, I was pointing out it's useful to see how many hops it's taking to get to your destination, useful to see the bottleneck.

And as a certified CISCO network engineer I DO know exactly what I'm talking about.

Edited October 6, 2013 by marketsqhero

[Mackem]

Most useless Poll ever... surely this is just showing the most popular ISP's site users use...

[clarkete]

Ok as simple as it gets:

Your browser talks to your router, your router has a DNS server address that is defaulted to a DNS cluster owned by your ISP.

http://glastonbury.seetickets.com

Means absolutely nothing until that name has been resolved by the DNS server owner by your ISP. It's them routed by your ISP to the correct IP of the Seetickets load balancer.

See how many references to "your ISP" are in there? It totally makes a difference as to how hammered your ISP DNS servers are because that happens well before you hit Seetickets.

The edit the hosts file trick works because you resolve the name to the IP locally without using the DNS server.

Overloaded DNS owned by your ISP means you can't resolve the address and THAT is a bottleneck before anything else happens.

Also doing a Trace Route to the name will show you how many hops it needs to go through before hitting the See servers. Bad routing could mean extra hops and slower response.

Edited October 6, 2013 by clarkete

[smudger]

I don't know if this makes any difference but I was the only one out many, many people to through in my group.

My PC and another pc in my flat that got through on the same ISP (plusnet)

Unlike everyone one else I have a different DNS. Its one I pay for, a few quid a year but means I don't have the public one assigned to me by my ISP.

I know this is only one small link in the process but every year it seems its my PC that gets through.

[Leggins]

Pointless poll which only shows which are the most used ISP in the UK and nothing else.

[Mattty]

I work for Plusnet so I thought I'd best defend our guys' honour here. I got 2 batches of tickets just fine.

Your broadband speeds are pretty much dependent on how close you are to your exchange. Conspiracy theories saying that one is worse than the other is daft.

[Hello... I'm Johnny Cash]

I had 6 devices and 3 internet connections. The one that got through was my iPad using Chrome connecting via a Three mobile hotspot.

It may have been blind luck, but the 2 devices connected to that hotspot seemed to fair quite a lot better.

[Thearg]

Nothing for the first half hour,kept on getting redirected but then got onto the holding page and got 6 twenty minutes later.

Happy days!

Oh and had just one laptop with the one window open on Sky broadband.

There was 4 out of the six trying.

[Penrhos]

Virginmedia 120M and it might as well been dial up. Absolutely nothing sat at holding page until sold out...

However got through twice on 3G phone and got 8 tickets.

[artl]

OR, it could be the ISP's throttling the connection to Seetickets. Thinking it was a DNS attack, automatically detecting.

[GingerRock]

AOL here. Not a sniff of a connection to seetickets from 9 until sold out. Worst year ever for me.

Edited October 6, 2013 by GingerRock

[thewayiam]

virgin, got in and out twice by just after 10am. others in my group got nowhere bear the deposit page other other ISP's but I'm not saying that's got anything to do with it. It is funny though how I've got through the last 3 times and the others haven't.