no 17 connection

[Empty_5oul]

right now i am getting no SOB connection just server time out error and host name not resolved erros, block added to submit queue.

Just checking if this is the same for everyone else ??

[chaz]

Same here

[AMDave]

I have been getting the same problems, so I referred to the thread on their forum that occurred when their DNS got switched back in January...
[ed]
http://www.free-dc.org/forum/showthr...&threadid=8348
[/ed]

I cleared the DNS cache and then did some lookups.

It appears that some of the DNS servers are giving the wrong IP address for the sb client site, and some are not finding the site in their registers at all.

I switched to using their direct IP address for the interim and all my clients are working ok. I hope their IP doesn't change in the next 24 hours.

Whatever the problem is/was it should resolve itself inside of 3 days, like last time, as the refreshed DNS entry re-cascades through the DNS servers.

[Empty_5oul]

k, gd gd.

i wonder why they keep moving stuff around and messing the numbers up :S

looking at the stats it only effected some of us, beer was fine and has submitted every hour in the past 24 - must be depending on which state/Country you are in

[AMDave]

yep. depends on the DNS server your ISP provides.

[AMDave]

ah. there is more to this than meets the eye...
check out their overall project stats graphs
http://www.seventeenorbust.com/stats/
(note this will only be relevant until they fix whatever the problem is)

there is now a new thread in the SoB forum regarding the current problem...
http://www.free-dc.org/forum/showthr...&threadid=8524

[Empty_5oul]

the servers appear to be going up and down as things are changed and they refresh across the world.
I am gonna just leave it all and then it will connect later as everyhting is repaired and live again, easier than changing the settings.

[AMDave]

That's what I did last time they had a DNS problem in Jan. After a while the renewed DNS cascaded again across the world.

Although, last time was not actually caused by a DNS failure, simply that the DNS name had expired and had to be renewed. This time....we'll wait and see what their admin's find.

[Beerknurd]

I take it that everyone's client are working now...??

[Empty_5oul]

yep i am back to sending every hour, guess the problem solved itself as it refreshed across all the servers.