Computer Test - Well Worth Trying...

Hi Everyone

Having worked through the latest nameserver issues at work it suddenly dawned on me it might well be a good idea to make other people aware of potential problems they may face.

So without being too technical I'd suggest a quick visit to this site and run the test for yourself: -

https://www.dns-oarc.net/oarc/services/dnsentropy

Hopefully you will see both results come back as being Great - if not your ISP has yet to update their systems and you run the risk of having false information being given to you from their nameservers taking you off to what you think is the normal website but infact isn't.

Any probs feel free to give me a holler.

Bryan

Forgot to mention the exploit is now general knowledge so the August 7th date for revealing how it works on this page is a tad out of date.

Passed

# 94.74.65.68 (indnsc40.ukcore.bt.net) appears to have POOR source port randomness and GREAT transaction ID randomness.
# 194.72.0.98 (indnsc60.ukcore.bt.net) appears to have POOR source port randomness and GREAT transaction ID randomness.

Good old BT

Two poors - two greats.

Everything still works OK.

Can't be bothered tbh.

Great and Great with Eclipse

I'd be more concerned with two poors on one nameserver I should add

Originally Posted by GhostyDog

# 94.74.65.68 (indnsc40.ukcore.bt.net) appears to have POOR source port randomness and GREAT transaction ID randomness.
# 194.72.0.98 (indnsc60.ukcore.bt.net) appears to have POOR source port randomness and GREAT transaction ID randomness.

Good old BT

Exact same result for me but prob because I am with BT as well.

Two poors, two greats for Virginmedia (ex blueyonder)

All mine were great.

Originally Posted by GhostyDog

# 94.74.65.68 (indnsc40.ukcore.bt.net) appears to have POOR source port randomness and GREAT transaction ID randomness.
# 194.72.0.98 (indnsc60.ukcore.bt.net) appears to have POOR source port randomness and GREAT transaction ID randomness.

Good old BT

Got the same with Virgin Wasnt surprised one bit.

All great thanks to Sky

I guess this is good! (But I had three results... )

194.168.8.110 (winn-dnsbep-2.server.virginmedia.net) appears to have POOR source port randomness and GREAT transaction ID randomness.

86.28.88.129 (aztw-dnsany-1.server.virginmedia.net) appears to have POOR source port randomness and GREAT transaction ID randomness.

194.168.8.109 (winn-dnsbep-1.server.virginmedia.net) appears to have POOR source port randomness and GREAT transaction ID randomness.

Great, and Great.: AOL have finally got it together again at last? Is that what it's all about? Good E'Nuff for me anyway.:

i have no idea what this means [the XXX i have put in]:

XXX appears to have POOR source port randomness and GREAT transaction ID randomness.

XXX appears to have POOR source port randomness and GREAT transaction ID randomness.

Is this good or bad? Rarely does the word 'poor' mean good, mind

g

Originally Posted by rayq81

All great thanks to Sky

+1

Does anyone know if port randomness is terminally bad? And what we should be doing about it? Clues please vela blue.

I'd really hate to have to stop talking to you all...... Byyeeeeee

Originally Posted by scsc

Does anyone know if port randomness is terminally bad?

I think I'd fall asleep if anyone really tried to explain it.

Paul.