What's new
Fantasy Football - Footballguys Forums

Welcome to Our Forums. Once you've registered and logged in, you're primed to talk football, among other topics, with the sharpest and most experienced fantasy players on the internet.

Why wasn't I able to get onto Footballguys at all today? (1 Viewer)

I was having issues too but I'm pretty sure it was me. Either that or it just happened to start working right after I reset my modem.

 
I couldn't get on this morning either. One of the most important fantasy football days of the year! :goodposting:

 
Our webhost made changes to their DNS servers last night. This was an update that they promised would not cause any downtime and it was a sitewide update that was not done at our request. However, as a result of these changes, our webhost introduced intermittent issues into the DNS resolution for Footballguys.com.

We placed a ticket with our webhost this morning when we discovered the issue. As of 4:17 PM this evening, our webhost believes they have diagnosed the root cause of the issue, but it has not been completely fixed yet. Over the course of the day, resolution seems to have improved markedly, but I am still seeing occasional DNS resolution issues locally on my PC.

If this were to happen again, the best workaround would be to add the following entries into the HOSTS file on your PC:

74.54.215.200 forums.footballguys.com

74.54.215.198 footballguys.com

74.54.215.202 forumimages.footballguys.com

74.54.215.201 images.footballguys.com

74.52.55.2 subscribers.footballguys.com

74.54.215.198 news.footballguys.com

The reason this would resolve the problem is that the entries in a PC's local HOSTS file override the entries in DNS, so if a HOSTS file entry exists for a URL hostname, no DNS resolution is attempted.

Here's how to edit your HOSTS file:

Windows Vista: http://www.mvps.org/winhelp2002/hostsvista.htm

Windows XP: http://www.fpweb.net/support/webhosting/ho...ing.support.asp

 
Last edited by a moderator:
Our webhost made changes to their DNS servers last night. This was an update that they promised would not cause any downtime and it was a sitewide update that was not done at our request. However, as a result of these changes, our webhost introduced intermittent issues into the DNS resolution for Footballguys.com.

We placed a ticket with our webhost this morning when we discovered the issue. As of 4:17 PM this evening, our webhost believes they have diagnosed the root cause of the issue, but it has not been completely fixed yet. Over the course of the day, resolution seems to have improved markedly, but I am still seeing occasional DNS resolution issues locally on my PC.

If this were to happen again, the best workaround would be to add the following entries into the HOSTS file on your PC:

74.54.215.200 forums.footballguys.com

74.54.215.198 footballguys.com

74.54.215.202 forumimages.footballguys.com

74.54.215.201 images.footballguys.com

74.52.55.2 subscribers.footballguys.com

The reason this would resolve the problem is that the entries in a PC's local HOSTS file override the entries in DNS, so if a HOSTS file entry exists for a URL hostname, no DNS resolution is attempted.

Here's how to edit your HOSTS file:

Windows Vista: http://www.mvps.org/winhelp2002/hostsvista.htm

Windows XP: http://www.fpweb.net/support/webhosting/ho...ing.support.asp
Yeah, but if it were to happen again I wouldn't be able to get here to find this post. :thumbup:
 
Last edited by a moderator:
Our webhost made changes to their DNS servers last night. This was an update that they promised would not cause any downtime and it was a sitewide update that was not done at our request. However, as a result of these changes, our webhost introduced intermittent issues into the DNS resolution for Footballguys.com.

We placed a ticket with our webhost this morning when we discovered the issue. As of 4:17 PM this evening, our webhost believes they have diagnosed the root cause of the issue, but it has not been completely fixed yet. Over the course of the day, resolution seems to have improved markedly, but I am still seeing occasional DNS resolution issues locally on my PC.

If this were to happen again, the best workaround would be to add the following entries into the HOSTS file on your PC:

74.54.215.200 forums.footballguys.com

74.54.215.198 footballguys.com

74.54.215.202 forumimages.footballguys.com

74.54.215.201 images.footballguys.com

74.52.55.2 subscribers.footballguys.com

The reason this would resolve the problem is that the entries in a PC's local HOSTS file override the entries in DNS, so if a HOSTS file entry exists for a URL hostname, no DNS resolution is attempted.

Here's how to edit your HOSTS file:

Windows Vista: http://www.mvps.org/winhelp2002/hostsvista.htm

Windows XP: http://www.fpweb.net/support/webhosting/ho...ing.support.asp
Yeah, but if it were to happen again I wouldn't be able to get here to find this post. :lol:
It's kinda ironic, but I thought of the same thing this morning. "Why not post the instructions on how to edit the HOSTS file on the site?" "Well, because the problem is that the folks experiencing the issue can't get to the site." :thumbup:
 
Our webhost made changes to their DNS servers last night. This was an update that they promised would not cause any downtime and it was a sitewide update that was not done at our request. However, as a result of these changes, our webhost introduced intermittent issues into the DNS resolution for Footballguys.com.

We placed a ticket with our webhost this morning when we discovered the issue. As of 4:17 PM this evening, our webhost believes they have diagnosed the root cause of the issue, but it has not been completely fixed yet. Over the course of the day, resolution seems to have improved markedly, but I am still seeing occasional DNS resolution issues locally on my PC.

If this were to happen again, the best workaround would be to add the following entries into the HOSTS file on your PC:

74.54.215.200 forums.footballguys.com

74.54.215.198 footballguys.com

74.54.215.202 forumimages.footballguys.com

74.54.215.201 images.footballguys.com

74.52.55.2 subscribers.footballguys.com

The reason this would resolve the problem is that the entries in a PC's local HOSTS file override the entries in DNS, so if a HOSTS file entry exists for a URL hostname, no DNS resolution is attempted.

Here's how to edit your HOSTS file:

Windows Vista: http://www.mvps.org/winhelp2002/hostsvista.htm

Windows XP: http://www.fpweb.net/support/webhosting/ho...ing.support.asp
Yeah, but if it were to happen again I wouldn't be able to get here to find this post. :thumbup:
Appreciate the info Memphis, but sending out an email ahead of time with this info, especially with most everyone in the playoffs would have made the day a lot less aggravating.
 
Our webhost made changes to their DNS servers last night. This was an update that they promised would not cause any downtime and it was a sitewide update that was not done at our request. However, as a result of these changes, our webhost introduced intermittent issues into the DNS resolution for Footballguys.com.

We placed a ticket with our webhost this morning when we discovered the issue. As of 4:17 PM this evening, our webhost believes they have diagnosed the root cause of the issue, but it has not been completely fixed yet. Over the course of the day, resolution seems to have improved markedly, but I am still seeing occasional DNS resolution issues locally on my PC.

If this were to happen again, the best workaround would be to add the following entries into the HOSTS file on your PC:

74.54.215.200 forums.footballguys.com

74.54.215.198 footballguys.com

74.54.215.202 forumimages.footballguys.com

74.54.215.201 images.footballguys.com

74.52.55.2 subscribers.footballguys.com

The reason this would resolve the problem is that the entries in a PC's local HOSTS file override the entries in DNS, so if a HOSTS file entry exists for a URL hostname, no DNS resolution is attempted.

Here's how to edit your HOSTS file:

Windows Vista: http://www.mvps.org/winhelp2002/hostsvista.htm

Windows XP: http://www.fpweb.net/support/webhosting/ho...ing.support.asp
Yeah, but if it were to happen again I wouldn't be able to get here to find this post. :cry:
It's kinda ironic, but I thought of the same thing this morning. "Why not post the instructions on how to edit the HOSTS file on the site?" "Well, because the problem is that the folks experiencing the issue can't get to the site." :lol:
Easy enough to do an nslookup though. :thumbup:
 
Our webhost made changes to their DNS servers last night. This was an update that they promised would not cause any downtime and it was a sitewide update that was not done at our request. However, as a result of these changes, our webhost introduced intermittent issues into the DNS resolution for Footballguys.com.

We placed a ticket with our webhost this morning when we discovered the issue. As of 4:17 PM this evening, our webhost believes they have diagnosed the root cause of the issue, but it has not been completely fixed yet. Over the course of the day, resolution seems to have improved markedly, but I am still seeing occasional DNS resolution issues locally on my PC.

If this were to happen again, the best workaround would be to add the following entries into the HOSTS file on your PC:

74.54.215.200 forums.footballguys.com

74.54.215.198 footballguys.com

74.54.215.202 forumimages.footballguys.com

74.54.215.201 images.footballguys.com

74.52.55.2 subscribers.footballguys.com

The reason this would resolve the problem is that the entries in a PC's local HOSTS file override the entries in DNS, so if a HOSTS file entry exists for a URL hostname, no DNS resolution is attempted.

Here's how to edit your HOSTS file:

Windows Vista: http://www.mvps.org/winhelp2002/hostsvista.htm

Windows XP: http://www.fpweb.net/support/webhosting/ho...ing.support.asp
Yeah, but if it were to happen again I wouldn't be able to get here to find this post. :D
Appreciate the info Memphis, but sending out an email ahead of time with this info, especially with most everyone in the playoffs would have made the day a lot less aggravating.
Exactly!!!!!!!! :thumbdown:
 
Our webhost made changes to their DNS servers last night. This was an update that they promised would not cause any downtime and it was a sitewide update that was not done at our request. However, as a result of these changes, our webhost introduced intermittent issues into the DNS resolution for Footballguys.com.

We placed a ticket with our webhost this morning when we discovered the issue. As of 4:17 PM this evening, our webhost believes they have diagnosed the root cause of the issue, but it has not been completely fixed yet. Over the course of the day, resolution seems to have improved markedly, but I am still seeing occasional DNS resolution issues locally on my PC.

If this were to happen again, the best workaround would be to add the following entries into the HOSTS file on your PC:

74.54.215.200 forums.footballguys.com

74.54.215.198 footballguys.com

74.54.215.202 forumimages.footballguys.com

74.54.215.201 images.footballguys.com

74.52.55.2 subscribers.footballguys.com

The reason this would resolve the problem is that the entries in a PC's local HOSTS file override the entries in DNS, so if a HOSTS file entry exists for a URL hostname, no DNS resolution is attempted.

Here's how to edit your HOSTS file:

Windows Vista: http://www.mvps.org/winhelp2002/hostsvista.htm

Windows XP: http://www.fpweb.net/support/webhosting/ho...ing.support.asp
Yeah, but if it were to happen again I wouldn't be able to get here to find this post. :thumbdown:
Appreciate the info Memphis, but sending out an email ahead of time with this info, especially with most everyone in the playoffs would have made the day a lot less aggravating.
Understood, Mr. Pack, and I apologize for the problems. We were trying to get a handle on the issue and neglected to send out this information to the mailing list. And the unpleasant side effect of building in the HOSTS entries in to your PC is that if we ever have to change the addresses of the servers, you won't be able to reach the servers without changing the information in your HOSTS file. At this point, my plan to solve this problem going forward is to find a third-party DNS host and add them in to the DNS rotation for Footballguys.com.
 
Yeh I wasn't able to log on either.

Really annoying since I purchased a subscription just last week for my leagues playoffs and I wasn't able to access the content this week at the last minute.

 
My link in Favorites wasn't working this morning for a while. I Googled footballguys and logged in through there. It was fine then. ;)

 
Was just able to log on for the first time since about 9 am this morning. Thanks for the paid information that couldn't be accessed. No updated info throughout the day. Deplorable from a customer service perspective IMO. A warning of some sort to alert us to the possibility of outages as well as workarounds PRIOR to the problem would have made much more sense, don't you think?

Sad.

 
Our webhost made changes to their DNS servers last night. This was an update that they promised would not cause any downtime and it was a sitewide update that was not done at our request. However, as a result of these changes, our webhost introduced intermittent issues into the DNS resolution for Footballguys.com.

We placed a ticket with our webhost this morning when we discovered the issue. As of 4:17 PM this evening, our webhost believes they have diagnosed the root cause of the issue, but it has not been completely fixed yet. Over the course of the day, resolution seems to have improved markedly, but I am still seeing occasional DNS resolution issues locally on my PC.

If this were to happen again, the best workaround would be to add the following entries into the HOSTS file on your PC:

74.54.215.200 forums.footballguys.com

74.54.215.198 footballguys.com

74.54.215.202 forumimages.footballguys.com

74.54.215.201 images.footballguys.com

74.52.55.2 subscribers.footballguys.com

The reason this would resolve the problem is that the entries in a PC's local HOSTS file override the entries in DNS, so if a HOSTS file entry exists for a URL hostname, no DNS resolution is attempted.

Here's how to edit your HOSTS file:

Windows Vista: http://www.mvps.org/winhelp2002/hostsvista.htm

Windows XP: http://www.fpweb.net/support/webhosting/ho...ing.support.asp
Yeah, but if it were to happen again I wouldn't be able to get here to find this post. :D
It's kinda ironic, but I thought of the same thing this morning. "Why not post the instructions on how to edit the HOSTS file on the site?" "Well, because the problem is that the folks experiencing the issue can't get to the site." :mellow:
Easy enough to do an nslookup though. :thumbup:
I'll take your word on that. I'm sure nslookups are easy. Now I ask, WTF is a nslookup? And how do I do it?
 
I'll take your word on that. I'm sure nslookups are easy. Now I ask, WTF is a nslookup? And how do I do it?
"looks up" an IP address for a name. Start>Run. Type in nslookup. When the window comes up with the > sign, type in the website, such as forums.footballguys.com. It should reply with an IP address. You can also do lookups on sites like kloth.net
 
I'll take your word on that. I'm sure nslookups are easy. Now I ask, WTF is a nslookup? And how do I do it?
"looks up" an IP address for a name. Start>Run. Type in nslookup. When the window comes up with the > sign, type in the website, such as forums.footballguys.com. It should reply with an IP address. You can also do lookups on sites like kloth.net
Sweet! That's what I thought you meant. I always wanted to know how to do that. Why is it called nslookup instead of iplookup? Just curious.
 
I'll take your word on that. I'm sure nslookups are easy. Now I ask, WTF is a nslookup? And how do I do it?
"looks up" an IP address for a name. Start>Run. Type in nslookup. When the window comes up with the > sign, type in the website, such as forums.footballguys.com. It should reply with an IP address. You can also do lookups on sites like kloth.net
Sweet! That's what I thought you meant. I always wanted to know how to do that. Why is it called nslookup instead of iplookup? Just curious.
name service lookup. you're querying name servers for an IP address. you give it a name, it gives you a number.
 
I too couldn't get on for most of the day. Given that it was week 15, it was extremely unfortunate timing. Oh well.

 
Last edited by a moderator:
One of the shoes that the Iraqi journalist threw at Bush hit a vital internet cable and knocked the whole continent off line. If he had just hit Bush in the nose I'd have been able to read that Gore was out and could have started Jordan instead and won my league. Damn you, Muntazer! Damn you!

 
I was unable to access all morning, until around 4:30 PM. So basically, any last minute lineup decision that I wanted to make, on one of the most critical weeks of the fantasy schedule, was in fact made without any input from the site I paid for. Now, stuff happens, and I'm usually pretty tolerant of unintentional miscues. However, I find the behavior of FBGs management to be completely out of character, and totally unacceptable.

I did receive MAIL from FBGs today; the Sunday updates arrived at their usual time. That made me think that the problem was on my end, not theirs, and I spent, no wasted time trying to figure out what was wrong with my computers. It's absolutely unprofessional and awfully disappointing that no information was provided about this problem to the subscribers. It make me think honestly that FBGs may have expanded too far too fast, and that they need to hire a much larger staff of some kind. This is something they should have been all over from the moment they knew they had a problem, and the lack of any communication leaves the impression that there was nobody minding the shop. That I have to come here looking for a POST with some information is ridiculous. And some sort of technical info with instructions, is, frankly, not getting it done either. I'm not a techie, and I shouldn't need to be in order to get the content that I paid for.

So now, kindly tell me how much of a refund I'll be getting for your failure to provide the services that you contracted to give.

 
Our webhost made changes to their DNS servers last night. This was an update that they promised would not cause any downtime and it was a sitewide update that was not done at our request. However, as a result of these changes, our webhost introduced intermittent issues into the DNS resolution for Footballguys.com.

We placed a ticket with our webhost this morning when we discovered the issue. As of 4:17 PM this evening, our webhost believes they have diagnosed the root cause of the issue, but it has not been completely fixed yet. Over the course of the day, resolution seems to have improved markedly, but I am still seeing occasional DNS resolution issues locally on my PC.

If this were to happen again, the best workaround would be to add the following entries into the HOSTS file on your PC:

74.54.215.200 forums.footballguys.com

74.54.215.198 footballguys.com

74.54.215.202 forumimages.footballguys.com

74.54.215.201 images.footballguys.com

74.52.55.2 subscribers.footballguys.com

74.54.215.198 news.footballguys.com

The reason this would resolve the problem is that the entries in a PC's local HOSTS file override the entries in DNS, so if a HOSTS file entry exists for a URL hostname, no DNS resolution is attempted.

Here's how to edit your HOSTS file:

Windows Vista: http://www.mvps.org/winhelp2002/hostsvista.htm

Windows XP: http://www.fpweb.net/support/webhosting/ho...ing.support.asp
Pushback by FBG on this should have been harder. Changes during this weekend and next weekend should not have been done regardless of what was promised. Promises don't matter when users can't get to your site on one of the most important days of the year for most of your subscribers.This is like Wal-mart doing an upgrade of their computers the night before Black Friday.

No way their management would risk an issue regardless of what guarantees someone made.

JMO

 
If I connected my laptop to my phone, I could access FBG. I could not from my home wireless internet. I thought it was just a mystery IP ban.

 
I was unable to access all morning, until around 4:30 PM. So basically, any last minute lineup decision that I wanted to make, on one of the most critical weeks of the fantasy schedule, was in fact made without any input from the site I paid for. Now, stuff happens, and I'm usually pretty tolerant of unintentional miscues. However, I find the behavior of FBGs management to be completely out of character, and totally unacceptable.I did receive MAIL from FBGs today; the Sunday updates arrived at their usual time. That made me think that the problem was on my end, not theirs, and I spent, no wasted time trying to figure out what was wrong with my computers. It's absolutely unprofessional and awfully disappointing that no information was provided about this problem to the subscribers. It make me think honestly that FBGs may have expanded too far too fast, and that they need to hire a much larger staff of some kind. This is something they should have been all over from the moment they knew they had a problem, and the lack of any communication leaves the impression that there was nobody minding the shop. That I have to come here looking for a POST with some information is ridiculous. And some sort of technical info with instructions, is, frankly, not getting it done either. I'm not a techie, and I shouldn't need to be in order to get the content that I paid for.So now, kindly tell me how much of a refund I'll be getting for your failure to provide the services that you contracted to give.
Awesome. :confused:
 
Lot of whining in this thread.

Stuff happens.

Get over it.

God forbid you have to make lineup calls yourself.

 
I also had some issues hitting the site yesterday. As was mentioned in the post above, FFG's site was not down on their end. It was another company's DNS update which was done incorrectly that caused a problem.

I do agree though, that the end of the season weekends should be free of such "maintenance" work, since no-downtime work can sometimes cause issues. Albeit, I think we are all giving FBG's site way too much clout then they probably have with their web provider. Undoubtably, many sites controlled through that company's DNS server were probably screwed up yesterday.

The update does not sound very impacting though. Seems like an IT Murphy's Law type occurrance... Frustrating no less for those which had issues connecting, but I wouldn't be unloading on FBG's staff because the issue was caused by another company. Agreed FBG's could have done a few other things with using their email list, but hindsight is 20/20. I have no doubt FBG's will institute such a plan for any future website issues.

 
I apologize for the troubles that the folks had yesterday that couldn't get on. Most people could access the site but obviously there were folks that couldn't. It was beyond frustrating I'm sure for the ones that couldn't. Keith was pulling his hair out trying to resolve it yesterday morning but it was something we couldn't control. But that's not your problem - it's up to us to always have the site up 100% of the time and we failed to do that yesterday for some folks. I'm bummed about it and I apologize. We'll do everything we can to not let it happen again.

J

 
Why? Because they have all their resources in one basket.

Geek explanation:

All they need to do is add secondary DNS (not hosted at the planet!) for pennies a year and problem solved.

 

Users who are viewing this thread

Top