Gruss stops working!

[wizardofmann]

I hope it's OK to post this here as well, as I already posted it on the discussion section.

Over the last five days this problem has reared it's ugly head again The Gruss interface freezes and so does my bot. I have shut down and looked at event viewer which shows a warning and reads:

Name resolution for the name api.betfair.com timed out after none of the configured DNS servers responded.

I guessed it could be a problem with my internet provider. I reported the problem and they say they cannot see a problem with my connection

I am on the UK and Ireland markets only

Any ideas please

[Captain Sensible]

If your DNS servers are having problems resolving api.betfair.com you could override it in the hosts files or maybe switch DNS servers to something like googles DNS in your router settings

[wizardofmann]

Thank you for your response Captain.

Unfortunately I am not sure what are the hosts files, or how and where to access them or how to override them

I also should have mentioned that I do not use a router but connect directly to my internet providers receiver (If that's the right word for it?) I do have a router but only use it for my 2nd desktop which I use for results/browsing etc

[Captain Sensible]

The internet is a bit like a big telephone exchange of IP addresses. But it's a lot easier for people to type in something like api.betfair.com rather than the actual IP Address: 84.20.200.10 into a browser etc so computers use DNS (domain name servers) to keep track of the actual IP address and convert your api.betfair.com to 84.20.200.10 for you.

Like everything on the net not all DNS servers are equal so if the DNS you're using isn't reliable then you'd just amend it in your 'reciever' to a more reliable one like maybe googles own DNS servers. If you amend the hosts file you can add the address for api.betfair.com and your computer will go direct to the address and avoid calling the DNS server that may or may not be causing a problem.

Changing the hosts file is pretty simple and lots of stuff on the net, might be worth avoiding though if you're not too computer literate as it will set the address and if betfair ever change ip address (unlikely) you'd need to alter it again. Probably best to see if you can change DNS servers on your 'receiver' as most allow you to change them. I've always found googles DNS or OpenDNS to be reliable, internet providers do sometimes use DNS to block sites etc so not always best to use the one they've set as default.

[wizardofmann]

Thanks again Captain but I am still none the wiser From what I can make out you are saying that with my lack of understanding I may, putting it politely, mess things up. I have been doing a lot of research and one of the things that may well be causing my problem is a thing called Teredo tunneling. So as it is a simple process of disabling it in the command prompt, it is what I have done and will see if it makes a difference.

[Captain Sensible]

Think of the domain name server (DNS) as your secretary, you ask her to get Betfair on the line and she dials the right number. If your secretary isn't that reliable or gone to sleep it may take a while to connect to Betfair. So you either switch secretary to a more reliable one than the one your ISP has give you or you dial the number direct by amending the hosts file so it avoids using the secretary(DNS) at all.

Hopefully your Teredo tunneling should sort things out , I just suggested the DNS changes because you said they weren't being resolved in your events viewer and they're a relatively easy fix to cut out the taht extra step and avoid using the DNS for Betfair.

[wizardofmann]

Thanks again Captain. Will run the bot today, so will keep my fingers crossed