wow, talk about inconvenient

Unbelievable

Very unbelievable, to the point that it's not actually true.

*.facdn.net is a wildcard, that resolves to 70.33.186.221 for everyone. It has worked off and on for the last few days - getting upwards of 90% packet loss at times.

The failure is

16 CWIE-LLC.car2.Washington1.Level3.net (4.59.156.58) 52.429 ms 48.219 ms 52.867 ms
17 cr2.iad3.inforelay.net (70.33.180.254) 53.564 ms 49.705 ms 53.515 ms
18 cr2.iad2.inforelay.net (67.208.89.118) 50.151 ms 47.644 ms 55.127 ms
19 cr2.iad2.inforelay.net (67.208.89.118) 50.564 ms !X * *

And IP routing has nothing to do with DNS.

harik@wolf:~$ dig facdn.net ns a.gtld-servers.net
;; AUTHORITY SECTION:
facdn.net. 172800 IN NS ns95.worldnic.com.
facdn.net. 172800 IN NS ns96.worldnic.com.

harik@wolf:~$ dig d.facdn.net ns96.worldnic.com
;; ANSWER SECTION:
d.facdn.net. 7200 IN A 70.33.186.221

Can we get a straight answer that doesn't involve trying to bamboozle people with buzzwords? The intermittent downtime is completely incompatible with your answer of a DNS error - especially with a 2 hour refresh on your A record. PTRs are used for reverse DNS and don't impact attempting to connect to your site - although they are frequently used as authoratative in IP allocation.

Still, it doesn't explain why www.FA.N (hosted on the same subnet) works while *.facdn.net is unreachable. That screams some sort of hardware problem, not "*coughmumbleDNScough*"

This seems to warrant a response.

agreed

I concur. DNS looks fine on my end for forward/reverse lookups for FA, even after a DNS flush. Still losing 64% of my packets to www.furaffinity.net (70.33.186.196) whether by name or IP (not that it matters - MTR only cares about IPs). Ditto for 186.221. And the packet loss happens between the 1st and 2nd closest upstream routers (66.231.180.84 and 66.208.89.118 respectively). So it's not FA. It's a couple of devices in ISP-land.

Smells like a routing loop to me.

pinging them during the whole downtime (*186.196 address) on a simple 1s loop and everything is fine, then down for 15 - 30 minutes in stretches (7k/ms timeouts) however, with the same internet company in a different physical location, my packet losses are still at 20 - 45% (home), and nearly nothing (at work) and that's with a response time averaging 74 - 76ms when it works. As I write this I'm watching it still fail considerably so I'm holding out until it comes back. usually tracerts come good but yeah, still having issues on the last 2 - 4 hops normally after the washington1.level3 sets is when it has issues.

not only that, but I still don't see why an IP would be randomly issued to someone else if one person has it first. especially if that person has had it for (months? years?)

If DHCP is involved (the thing that assigns IP addresses dynamically and keeps track of them), and they have more than one DHCP server that isn't talking to the other, that could result in IP collision. But I doubt that's the problem -- when the issue manifests, it's too far upstream from FA's server to be something where DHCP is involved. Network gear usually gets static IPs.

because YOU totally know what you're talking about, right?

I don't see you posting any useful information, whose to say they don't? There's plenty of capable people on this site who know just as much if not more than the FA who contorl this site when it comes to things like this.

I can back them up, its my field of study.

Also it is good thar people question the authenticity of what companies or individuals are shoving down their throats.

...which is exactly why I'm questioning him. How do I know that he knows what he's talking about?

How do you know the FA admins know what they're talking about? If you don't understand the technology (which is fine, most people wouldn't) you have to rely on other means to judge who does know what they're talking about. Somewhat like reading the news, you have to trust reporting is truthful, balanced and accurate, when most of the time none of us are experts on any given story, so you have to look for other clues to determine if a story is accurate. Who you believe here is your call if you don't understand what either party is saying, but do consider harik's response isn't just some angry rant. He/she has tried to offer some proof of another root cause, and I would concur the explanation given by FA is... wonky at best, to be polite.

harik's response makes sense while FA's sadly doesn't. Or at least, FA's response looks confused. It might satisfy people who wouldn't understand this stuff but it doesn't satisfy those of us that do. It's probably not intended to be deceitful, but as it's written, it just doesn't give any meaningful information or even make sense.

DNS PTR records have absolutely nothing to do with accessing a website. In simple terms, DNS maps domain names to machine IP addresses. When you visit an address, your browser does a 'forward lookup', asking for an IP address from a name, so your browser knows where to connect to. Certainly, if DNS is broken in such a way that forward lookups fail, things stop working (although when things break this way, most people will see a message which hints at the problem very quickly, something to the effect of website can't be found or doesn't exist).

You can also go the other way - looking up a name from an IP address. This is the much lesser used-or-cared-about 'reverse DNS' and this is what the PTR ("pointer") records are all about. While some services often depend on reverse DNS working (such as email), ordinary websites do not. Anyone at FA in a position to change a PTR record can put it any name they wish. They can make all FA's IP addresses reverse-resolve to microsoft.com - and it wouldn't matter. PTR records just don't matter here. Nobody will notice unless they really go looking. Similarly there can be no PTR record at all. That's just fine. Email may break, but not the site.

So to mention any problem with PTR records and suggest that a DNS change fixes this as it might with a 'regular' forward DNS screwup... is nonsense. Most people won't know it. Some of us do. We're not special. We just do this stuff for a living.

I suspect somebody somewhere has their wires crossed, figuratively, or there's been a case of Chinese whispers. There's also mention of an IP conflict which is much more interesting. It MIGHT be that somebody other than FA have screwed up, and some of FA's IP's have been duplicated elsewhere. Maybe their ISP poorly manages them, and the DNS thing itself has nothing to do with it but could have been a symptom. I might expect very bad things to happen if some sort of IP conflict has occurred. If, say, somebody else has been able to update DNS PTR records for FA's IPs, that means somebody else may well have been provisioned those IPs as well, and that would be the real problem (in that scenario, DNS PTR record changes are a symptom, not a cause of a problem). At the moment that's the most sense I can make of it, based only on what FA and a few other people have said.

Or maybe FA's admins have been completely bullshitted to by their ISP, and themselves told of something or other involving DNS and PTR records, and relayed some already misunderstood message to us. I'd really hope that isn't the case though, but what we have been given, as it reads now, is basically nonsense.

It's also entirely possible something else has broken at the same time, and is being overlooked. Simultaneous failures can and do happen from time to time, and it can be easy to fixate on one cause - especially if somebody else like an ISP has given some sort of explanation already.

Curiously although FA is probably among the worst sites on the web for a vast list of reasons, it's been working absolutely fine for me during this whole incident.

"FA is probably among the worst sites on the web for a vast list of reasons"

I'd like to prove how wrong you are, but I don't have the time or the motivation to go searching the web for badly designed, immoral, or overall horrible web sites.

HEY!! Dont go dissin FA like that! Not only woild the full force of people and admin kick your ass but you could get on everyones shit list. Just sayin.

"DNS PTR records have absolutely nothing to do with accessing a website"

The combination of network range and PTR record is used by some automatic configuration systems. Without knowing more about their setup, we can't say this conclusively.

There does appear to be some other issue at play, but the pile on where some folks are calling the admins liars or incompetent isn't warranted based on as much information as has been presented here.

DNS is avoided like the plague in routing environments because it can fail and does fail quite often (you may not even notice it failing as well). If they are depending on DNS for routing related stuff, they are doing it wrong.

~ That guy who works for a major networking company.

Well it's obvious YOU don't, because what I posted was direct evidence that the line of bullshit you were being fed was a lie. It kinda speaks for itself if you know anything about how the internet works.

Well, I can vouch for you as well.

Off topic, what distro?

*shrugs* I only really know the basics, packet switching, that kind of stuff

Damnthats a good point.

because it's impossible for people aside from fa admins to know this kind of thing

sorry, man. I tend to argue a little too much *shrugs*

I think that while FA may not be the best site out there, I prefer its simple design (though a few features could be added) and I appreciate that the FA admins are looking into the problem. Whether or not they've found it is another story. Only time will tell.

Perhaps some people DO know more about what's been happening, but I sure don't. All I know is that it had to be something between the affacted users and the site itself, because I wasn't experiencing these problems, along with many others.

fa, as a community, isn't that bad of a site, not at all- it's a lot better than most obviously

but... it's still in like 2006 and older in terms of coding. it's really outdated and it needs a major makeover, things would stop breaking less if they just tore it down and rebuilt it or did something other than overlapping old code with new code but still probably breaking things in the process by doing that- i'm sure you've heard it all before so i won't really get into it

just.. try to not assume the fa admins are the only people that know this stuff- there are IT people and hell, computer geniuses that know a lot more than the admins do and i'm willing to believe there are users on fa who are more experienced. i've witnessed it myself when i've had to ask some people on fa for help regarding my computer so it's not impossible that these folks know what they're talking about u3u

given fa's history i wouldn't doubt they don't really know what's going on either, like the person above said maybe their provider is dicking them around or something who knows but still... that's no reason to doubt others like that!

agree

He partly knows what he's talking about.

His dig shows the current status of DNS, but tells us nothing about the previous state. The old configuration could well have had a very long TTL even if the current one is measured in hours. So there's no conclusive proof that the original post was not believed as true when it was written.

However, the intermittency that persists for some users (as per the many replies below) and the traceroute results some have shared suggest that there is a separate problem that has not yet been acknowledged by admins.

The dig command is definitely the most useful one of the bunch IMO.

Assuming they run linux with apache for their servers, I think the problem might lie within their apache configuration file. That would explain why one part of the site works, but another doesn't.

DNS records do factor into website issues. Specifically A Records and aliases to A Records whose name eludes me at this time. The aliases, however, have to be configured in the apache configuration to even work. Otherwise they will automatically redirect to the www subdomain.

My advice to FA dev team: check the DNS records and the apache configuration in /etc/httpd/conf.clients, make sure the IP addresses match up, use the dig command to double check everything.

Ahh yes DNS the wait no it has nothing to do with DNS.

16 CWIE-LLC.car2.Washington1.Level3.net (4.59.156.58) 46.963 ms 45.645 ms 48.080 ms
17 cr2.iad3.inforelay.net (70.33.180.254) 55.048 ms 51.986 ms 56.364 ms
18 cr2.iad2.inforelay.net (67.208.89.118) 52.598 ms 48.561 ms 51.073 ms
19 * * *
20 * * *

vs

16 CWIE-LLC.car2.Washington1.Level3.net (4.59.156.58) 46.393 ms 45.769 ms 46.324 ms
17 cr2.iad3.inforelay.net (70.33.180.254) 52.657 ms 51.315 ms 50.695 ms
18 cr2.iad2.inforelay.net (67.208.89.118) 47.107 ms 50.038 ms 47.777 ms
19 66.231.180.84 (66.231.180.84) 53.959 ms 51.660 ms 52.934 ms
20 www.furaffinity.net (70.33.186.196) <syn,ack> 54.957 ms 53.223 ms 52.504 ms

See hop 19? That's where shit goes wrong. That's not DNS related. Furafinity.net hasn't changed IP addresses between those runs, it's always at .186.196. If I had to speculate, .180.84 is either a router or load balancer with a flakey port, and someone with access to it can check it's logs and watch traffic on the port connecting to cr2.iad2.

Why are you still faffing on about DNS?

Oh man.
Well we will see how this goes down over the weekend.

well i think i'll just watch your avatar dance while waiting out the weekend then

Hahah, I get that alot lol

Yep! Me and a couple friends are still having some issues, but the connection is slowly starting to some back, it seems.

it keeps timing out that's about all

Interesting..

Thanks for looking into and resolving it!

Well... It loads after a couple minutes. Its inconvenient but I could be doing other things than being on the internet. Its alright, you're trying your best!

Hopefully tomorrow the problems I started to have with accessing FA on my iPhone this week have been fixed now.

Good update!

Hopefully all the issues will be sorted out soon!

I just checked and still having the same problems with accessing FA on my iPhone as before where I get time out errors and bad file descriptor errors.

I've also noticed it works on my laptop but won't load at all on my phone. I also have an iPhone.

I noticed it almost always times out when I try to load normally, but when I load through BoomProxy it loads up almost always, though uploading anything is then problematic :/

9 hours later- still getting these same issues. Tried to connect to fa from a different location, different town even- same issues. Different router and network all together.

Still broken in the same way.

traceroute to www.furaffinity.net (70.33.186.196), 30 hops max, 60 byte packets
...
14 ae-32-80.car2.Washington1.Level3.net (4.69.149.132) 31.338 ms 37.386 ms ae-42-90.car2.Washington1.Level3.net (4.69.149.196) 36.510 ms
15 CWIE-LLC.car2.Washington1.Level3.net (4.59.156.58) 34.242 ms 35.765 ms 34.891 ms
16 cr2.iad3.inforelay.net (70.33.180.254) 36.945 ms 37.323 ms 36.759 ms
17 cr2.iad2.inforelay.net (67.208.89.118) 35.934 ms 37.606 ms 37.699 ms
18 cr2.iad2.inforelay.net (67.208.89.118) 37.259 ms !X * *

It's like this off and on all day, cr2.iad2.inforelay.net is always the failure point. None of my testpoints trace to you through any other path, so I'm not sure how it's working for you guys. !X is "Communication administratively prohibited" so probably losing it's route and dropping your subnet into the bitbucket.

When it works it has two more hops:
19 66.231.180.84 38ms
20 www.furaffinity.net (70.33.186.196) 29ms

Tracing from a working location goes through the following:

13. cr2.iad1.inforelay.net 0.5% 378 29.6 35.9 28.2 216.5 28.2
14. cr1.iad2.inforelay.net 0.5% 378 28.9 35.6 28.3 236.7 26.4
15. 66.231.180.84 0.0% 378 30.0 30.0 28.3 34.2 0.9
16. www.furaffinity.net 0.0% 378 29.2 29.3 28.3 32.0 0.6

Note it's a slightly different set of routers - cr2.iad1->cr1.iad2 vs cr2.iad3->cr2.iad2.

cr2.iad2 is extremely broken and you need to yell at your provider until they fix it.

Good, because as of a few minutes ago, this is still happening. And my connection to FA is always being routed through cr2.iad2.inforelay.net both when it's working and when it isn't.

Er, "none of my testpoints trace to you through any other path" is obviously wrong, since I explain exactly where the path difference is. I wrote that before I found one that came in a different path and forgot to take it out.

https://www.furaffinity.net/journal...../#cid:34291211

Other people backed up what you're saying in the previous journal and it went unanswered.

all this time, I've had no issues with fa. interesting.

yaaaay thank you

No problems for me...

FA having connection problems?

You don't say...

But from roughly September 2012 to May 2013, the site had a big issue with pages taking 15+ seconds to load.

That could also be your computer, you know. I haven't noticed any connectivity issues during the time frame you mention except for this one just recently.

It's not my computer. The connectivity problems happened on every device I had, and numerous other people reported having the same issue.

Even if that is true, it still wouldn't warrant snarky, self-entitled comments. You have access to this site, for free, which is managed and run completely by other people.

I don't particularly see the comment as snarky; one of my friends says this site is notorious for slow loading times.

Yes, a free site that's poorly managed with inadequate staffing and hardware

The average person isn't that knowledgeable about network issues, but I think they'd realize that if one web site is slow and every other web site works fine... it's probably not their computer that's the problem.

Technically inclined people really need to stop barking at users for being stupid. FA is slow during USA daylight hours. This is no secret.

It wasn't so much my intention to say they were unknowledgable or stupid. But I think that people, technically inclined or not shouldn't whine and make negative comments simply for the sake of being put out as if they're entitled to anything.
Even if the site is slow, even if it's poorly managed, it's not our site. We don't help run it, and aside from people buying ad space or donating we don't pay to keep it running. There is no membership fee, we're not on staff or buying hardware. We're not shareholders or investors either.
This site doesn't owe any of us anything, was more my point, and while companies and individuals rely on constructive user imput to resolve issues and make improvements, that is very different from people constantly whining about how bad this site is when they're offering no help to fix it and have nothing to do with it's operation.

My response was directed at 'tone', not 'knowledge'.

For future reference, pretty sure it's FA:
http://habnab.it/fa/1year/

There are no problems from my side.

I've not had any more problems on my cell phone, but i still have issues on my pc.

I'm still having issues but I ain't worried you guys know what you're doing

Haha, that was a good joke!

Thank you very much! This is faster than I could imagine you getting this resolved or finding the problem.

THANK YOUUUUUUUUU \^w^/

Ahahaha irony. I've been fine most of the time (had a couple hiccups a few days ago for part of one day but then was fine again) ...and now I'm having hiccups with the errors.

What are the odds of getting the same IP as someone else I wonder.

No connectivity issues for me, but still can't upload anything, even an avatar. :|

Meanwhile at FA HQ...

Meanwhile at HTS.

thanks!

I'm still having problems, and will let you know by tomorrow if they are still continuing.

Thank you all greatly for addressing this problem. If my problems persist, I'll contact whomever I can. Thank you again!

it seems to have worked. I'm still having a few loading lags (like 30 secs instead of 10) but havent had any timeouts all day

Thanks for getting it fixed guys :D

Ohh I thought it was just my Internet or something x3 hope it get fixed soon though, it's kinda annoying :/

issues still abound on my end, i`ll keep you posted.

It took 25 minutes worth of attempts just to load the login page right now, it's most certainly not fixed yet

The problem's not fixed. You had someone tell you already that it's your load balancer/hardware firewall breaking down on you, not a DNS issue.

Besides, if another website's domain name got assigned your IP, the people going to that domain would just go to FA instead. That's how DNS works.

I'm still experiencing a few issues here in KY, but hopefully this will resolve itself soon.

That might explain why I've been having issues then

Same here. Hopefully this will resolve by the time I get up tomorrow.

Same here, too. The connectivity is still intermittent, at best, and I can't browse through the site without having pages time out on me.

hopefully tomorrow this will be fix, im still getting timeouts

Hope this works. Its annoying to wait for nearly six or seven minute before the page actually loads.

Mine still has me reloading 15-20 times before getting to the site, hopefully this will be fixed soon.

Still not fixed for me. If I don't meet my weekly porn deficit, I don't know what I'll do....

This might explain the small numbers I was getting on some of my pics over the last week. Good to know it's being fixed!

It happens. Thanks for the update!

I'll let you know if I'm still having trouble not later than 0730 ET 6/22.

Does knowing our ISP work?

I'm still having some issues on my end, though it isn't anywhere near as bad as it was a few days ago.

Still having issues on my end as well. If it doesn't resolve by tomorrow I'm going to assume the problem wasn't actually fixed.

so far still hanging at the same IP (67.208.89.118), but for a lot longer now. 20 min at a time instead of 5.

Will report as it further develops, unless it gets to the point that I can't even get on here.

Cool, thanks. Still doing it at this time, btw.

still locking up at the same IP, even after a forced reboot due to a power outage

still doing it, same IP

Want to know something really weird? I'm using FA on my iphone, and when I access it on the cellular data connection is when it has the most trouble with timeouts. But if I join the home wifi, the connection problems almost stop. And my cellular connection is more reliable than my home network. I know joining a network makes it use the gateway/router's connection and address as opposed to the iPhone's 3G broadband modem. It's just weird how it will work on one connection and not the other.

2nd'd. I'm having the same issue.

I have noticed that the problem has occurred more often when on my smart phone. I will be curious to see if it resolves on the phone too.

I host professionally and thats just unheard of! Someone did not do their job correctly! They don't need their job apparently! XD

It seems to have been working ok for me today (though I just woke up and saved my submissions). Hope it is fixed indeed, thanks for looking into it.

Still having issues. Will see how it does tomorrow.

Also still having the issues. We'll see how it is by tonight.

Been trying to connect since I saw the original journal a few hours ago, hopefully things stay stable but I'll make it a mission to let it be known on the forums if I cannot connect or stay connected come tomorrow or later in the day.

Youll only see the users on Dragoneer's naughty list with connectivity issues

Still havin' problems. :/

Issue not resolved on my side.

Still having problems here still.

it is being stupid for me still but i have managed to grab on for a bt i hope it keeps like thisand stays fucking stable

I never noticed any connectivity issues on my end, but maybe I just wasn't online enough. =P
Either way, I'm glad you guys are doing something about it, I'm sure it means a lot to some people. ^^

8:42 AM here in Kentucky, and still having problems on my end.

I dont understand anythang you nerds are talkin abou

It seems that i can access fA on my desktop but not my laptop i do not understand this reason i use my laptop more.... hopefully this gets resolved it is rather bothersome.

It is 9:00 on June 21st here and I'm still getting timeouts when connecting to FA.

the issues are on and off for me ..

Well whatever the issues are caused by, they're still affecting me and have been for about a week.

Thank you so much. Haven't had issues since I came to my parents otherwise I would have been sending you a note as well.

Unlikely he would of seen the note anyway. The one I sent from the last journal was never read.

You have a good point.

dud love the skyrim shout icon its awsome

Mine says needs gallery folder and then i click the link to fix it and it still wont work...

6/21/13

Still acting up as of this morning.
Works well one time, then stalls, then works again a few minutes later.
Hopefully the DNS will resolve soon.

Thank you for your support.
Your efforts are highly appreciated by this particular dragon.

Kindest regards;

}:>

PS: Took several attempts, and time outs, to submit this reply . . .

Better than it was yesterday...but it still goes.

Still timing out for me too.

It's nearly 1:30 EST and I'm still experiencing frequent timeouts.

It seems for me the problem is much worse.. I'm getting multiple timeouts on several different devices and networks still.. I'm lucky if I can even get on FA at all. It's usually working for 5 minutes, then down for 20 or so.

I dunno, but I have to agree with Harik on this, it doesn't sound like a DNS issue. If anything, I think it may be some sort of hardware or software configuration / glitch on server side, hardware that is faulty, or not responding correctly.

I mean, I'm even noticing longer load times even when the site is up and running for me, and I have FiOS (50 Mbit) internet speeds. I usually never see slow load times..

FA's page generation time for me though (whenever it works) is up to almost ".800" seconds. I usually have the page generate in under ".100". I even get almost ".800" under non-peak times of day, and even non-peak days too where people usually aren't on.

I'm starting to think something else may be the culprit, just my two cents.

I'm still having issues with connection really bad, it has taken me 20 minutes just to get here so I can say something!

I'm still having problems uploading music.... It's the right type of file, but it always says connection reset. I've tried different browsers, (like internet explorer, firefox, etc.) it works great, but JUST on that one thing... :( anyone else with this problem?

Having minor issues, I've just decided not to be on FA much for today cause of it! I need to go save the world anyways.

Still having issues with this, almost been two weeks now.

Still having issues. took forever to load, timed out 3 times

I'm not concerned about the issues on the laptop I'm using at my aunt and uncle's house because I'll be home tomorrow.

DNS has propagated by now. Same issues as before. Get a handle on this guys or find a new provider. I was unaware this is what my donations got me.

Issue continuing to happen on my side.

Still having connection issues. It works fine for a few minutes, and then I'm timed out for at least 10.

I'm still experiencing problems loading all FA pages, including this journal. No problems anywhere else. :(

"The connection has timed out

The server at www.furaffinity.net is taking too long to respond."

Connection is still random

It's almost unusable here still :(
Works perfect for a while, then goes down for 10-15mins at a time

Guys, that took you long. XD
What do we learn?
Not just code needs debugging at times =)

Some advise - always keep your DNS in your eyes, it loves to get messed up, especially when you have a few NS providers.

Reading back the comments...god you guys are bad. XD

How many of you FA-runners actually know how to handle DNS... :p

Just do this...erase all zone files, re-write them from scratch, period. :)

... when you're talking about DNS it's satire, right? I can't keep track of who's mocking the inability to operate a website and who's genuinely clueless.

DNS is the service that translates a name, in this case furaffinity.net, into an IP. This service is terribly broken for FA currently.
Im not respective for the site, I just am kinda amoused by how slow their fix-up is going... but then again, I never heared the FA team and the word "speed" or "fast" in the same sentence :p

They out to hire you. XD

At least I would know what to do apeparently... XD

Holy fuck. I mean, holy fuck shit cuntkicking dickdildos I don't have enough cursing to properly express how amazingly terrible you are.

You really don't know anything about anything, do you? Like, I couldn't reach the site to respond to you for a week and I come back and find that you weren't actually being satirical about DNS, you really think you know anything about it at all and that it had anything whatsoever to do with the outage.

Were you the retard who thought that it was a DNS issue because the MX records weren't right? Or was that some other technologically illiterate jackass who felt the need to open their piehole.

It appears I know more than you :p
Check the most recent journal on this, then we talk again. :D

We had our host shut down the routing from from their secondary router (cr2.iad2.inforelay.net). The router is no longer active for FA, and should force people to route through the primary router (cr1.iad2.furaffinity.net) to connect to the site.

Hey shit for brains, explain what that has to do with DNS and MX records?

I won't keep everyone else in suspense: It doesn't. As I said, you just need to shut the fuck up and never ever discuss anything technical again, since you have absolutely no idea what you're talking about.

Seems like youre just a little underaged child, trying to proof a point; with invaild arguments. For once, I never talked about explicit record types - such as MX. Secondary, I'll just remind you, of what the routers in general do. Sure, they also route into the system and establish connectivities. But it looks like someone has to learn quite a lot about how things work - and that is appearently not me. Stop trying to argure like a little child, or I'll have to report you for harrassment in terms of the way you talk to me.

Still having issues

Still having issues here as well. :/
In fact had trouble even loading this journal, heh.

still happening here to

Im still having issues with fa

still having issues ._.

The connection issues are the same, if not worse.

still am

I am still experiencing these a bit... It's a bit annoying.

I am also still stuck in this connective issue mess....

Still having issues connecting to FA a few times today, but i have mostly been able to connect today. Like its saying "This webpage is not available" so am still having some minor issues with it. And i know its not my router or DNS since i can still connect to everything else perfectly fine.

Still having the connection troubles.. this all started a week ago and its more than a little irritating when you are just trying to clean up your message boxes only to have it die in the middle of it..

Same here. The site times out or won't load at all.

Same here, still having connection issues.

It's been days and I still have problems connecting to FA. Most of the time it times out. I already sent a trace route. Getting to become a massive problem for me.

It was even a problem just to get this replay message posted to this journal.

Yes, I cleared my cache and cookies already.

Lol we should have problems more often these comments are hilarious
But people please be patient.
Things have started working out for me btw.

Still having issues

Still having a fair amount of trouble.

nope, still broken

Still having the connection go out here. This is getting really inconvenient.

Still having really bad issues on my end but at least I can stay connected instead of it going out every time I switch pages.

it is still doing it maybe if you got staff who actually knows how to do its job we would never have this issue i keep having internet time outs and is extreamly hard to even reply to this this aint a dns issue this is just ya staff having shit hosts

24 hours have past..same issue still. :(

My iPhone seems to be having trouble. The site keeps crashing and when I'm on my computer the site will work fine one moment and the next take about a minute to two to load.

Still certainly an issue for me. It could be route flapping since connectivity starts and stops so often. Whether or not this affects a user would depend on the route taken to reach FA.

Is some sort of routing protocol enabled? RIP or OSPF? Check the load on the ferrox router and see if it's pegged; same thing goes for the InfoRelay router that seems to be where the problem occurs. I would have hoped someone would have seen all of this though. Same goes for a router or interface going online and offline repeatedly. I don't know how many routers FA has or if there's just the one for all of the "ferrox" network.

I doubt it's a load balancer issue since some users never have the problem at all.

This is probably just pissing into the wind though since I doubt any admin will keep reading this far.

I strongly doubt its the load balancer they use...I just belive they do have a strong issue with their InfoRely routers - or, Nameservers actually. One of their nameservers is delivering some wrong informations, or the server just outright blocks access via that IP. But what are these protocolls/programms you just mentioned, the RIP or OSPF? :o

RIP and OSPF are basically different methods of ensuring that all routers working together see the network topology identically; i.e. effectively route traffic in a consistent (and hopefully efficient) manner. Certain circumstances can cause a router to constantly recalculate how to route traffic causing a high load on the routers CPU and leading to bad routes that can't connect and/or a router that isn't responsive. This could be caused by hardware issues, a bad configuration, etc. I'd expect Inforelay to be able to spot a misbehaving router by now though. If they have some sort of monitoring going on a look at the router cpu loads would probably highlight any router having issues. I really don't know Inforelay or FA's configuration though.

Still having problems, in some cases chrome doesn't even try to load the page before the timeout error comes up.

Still having issues here. Works for a few minutes and then goes blank.

Pages only come up after refreshing about 5 or 6 times. It's actually worse than before, before I would only have to refresh once.

Yes, definitely still happening, and happening right now as I'm trying to view some images.

Still same issues and tracert shows same problem as before

Still having the same issues.

It's working for me But! It Breaks down after I Nuke all my messages

Rest of the site still works fine, BUT I still am unable to submit anything.

so far it is fine except for a few slow moments every now and then :)

Still having issues, but overall it's been working more often today than it has the past few days.

Every time i try TRY to fucking log in i get this over and over
The connection has timed out







The server at www.furaffinity.net is taking too long to respond.





The site could be temporarily unavailable or too busy. Try again in a few
moments.
If you are unable to load any pages, check your computer's network
connection.
If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.


fix this shit before i go to inkbunny

They're trying to fix it, relax. If you have any information that will help this situation, please feel free to speak up.

Also, making threats like "I'll go to inkbunny" is pretty moot. I'm sure they wont be crying themselves to sleep with a handful, let alone 1 person, walks off and frees up some space on they're hard-drives.

XML Parsing Error: unexpected parser state
Location: jar:file:///C:/Program%20Files%20(x86)/Mozilla%20Firefox/omni.ja!/chrome/toolkit/content/global/netError.xhtml
Line Number 305, Column 54: <div id="ed_netTimeout">&netTimeout.longDesc;</div>

---

^

This error comes up from time to time, instead of the 'standard' time-out these connection issues are causing. You guys still have stuff to fix.

This looks rather like something in your browser is broken rather than on FA.
An XML parsing error, on a local drive, could be some sort of addon you installed.

Look at the error though--it's an error with the time-out description!

Lolwut! XD I just saw. Now thats really weird I have to admit :D

Still having issues at this end just got it when I tried to comment a minute ago

It being the "Cannot connect" error asking me to reload the page I mean

Its still giving me the connect issue as well. I don't know what else to do...
*sigh* I hope this gets fixed soon.

Still broken, please fix it.

yep we still have issues too uvu

for those who can to flush old bad dns on windows::

win+r > cmd> ipconfig /flushdns > ipconfig /registerdns
^= removes old entries and requestsa new mapout.

doesn't work

still having issues

Nope didn't fix the problem.

I'm experiencing an issue in uploading a submission, fix plz?

I am still having difficulties even getting onto the main page. I hope this is resolved soon...

Still experiencing problems-- and I appear to be in much company.

Still having issues here as well, going to sleep and see if it's better in the morning.

still having problems too

FWIW, I'm still having connectivity issues too.

DO what ever ya'll did Helped me for about 24 hours then it started all over again.

sorry my computer flipped out and triple posted

My end is still having troubles :(

It got better but I'm still having issues... just not as much! At least its a start. Thank you for your hard work and best of luck on resolving this problem. ^^" -Sherb

i still cant put any pics, I hope they fix this soon.

You made it even worse. Getting timeouts more frequently.

blahblah DNS blahblah -
no change at all - its still the same ip. there is no szenario where something can propagate to us which brakes traceroute SOMETIMES.
do you have a broken dns server which cannot resolve some of OUR ips and blocking those connections sometimes when the query times out? maybe you want do try a locally caching dns-server like dnsmasq.

(zone serial 113031910)

Fun~

12 dca1.inforelay.net (208.173.12.130) 37.083 ms 34.144 ms 34.200 ms
13 cr2.iad3.inforelay.net (67.208.76.5) 23.454 ms 23.266 ms 23.174 ms
14 cr2.iad2.inforelay.net (67.208.89.118) 23.510 ms 23.584 ms 23.464 ms
15 cr2.iad2.inforelay.net (67.208.89.118) 23.551 ms !X * *

man traceroute: "!X (communication administratively prohibited)"

Still having the same problem.

Still having the same connectivity issues just like before, still with IP 66.231.180.84.

It got better for about two days, but when I woke up this morning, it was back to the 5 minutes online, 5 minutes offline thing again.

Been over 24 hours, still on slowdown. Actually feels more frequent now even at times.

Still having issues.

Still having issues this morning

Still having some issues. I am sorry to be a bother.

Still having the same issues, and it seems like they may be worse now.

well you see I would have replied sooner but when I hit post FA stopped working for me.
hmmhmmmhmhmmm

I am still having a some issues with the connection.

Been having gateway timeouts on my cell lately being on here.

Still having random connection issues here. In fact, it took several tries to send this comment.

Yep, still having issues :/

Socorro NM, over Century Link - still haveing problems here. No change since the "solution".

It's Saturday, and I'm still having connection issues. =/

The problem still persists

Still no little to no connectivity here in TN. Tried loading the site without a proxy server last night and just now and couldn't even get the main site to load to be able to report issues.

Still having the same issues here. The site varies inconsistently between being completely fine, being fairly slow, and being totally inaccessible due to timing out.

Yep, still having the same issue. Work for 5 minutes, then refuse to connect for 15 minutes, and so on.

I'm still getting intermittent connection issues too. I'm also getting the same pattern as Gelsh.

Still having lots of issues

I still have issues as well. Mostly with search, but I've had problems since Friday. I'm not worried though. It will work eventually. It's all about patience,.

Some of us have been patient since the 13th.

And you can't survive without it?

Still another 24 hours ... assuming THIS makes it to the posting list.

I'm still having issues. do you think resetting cookies would help?

Not at all.

Hey look, it's still not fixed. Maybe because it's not DNS and never was DNS and never has been DNS unless I somehow missed a memo in the past 20 years where DNS magically controls a firewall/load balancer. Hey look, it doesn't. And hasn't at any point in the past either.

Oh, and then there's the fact that it wasn't changed at all.

PREVIOUS (AND CURRENT) ASSIGNMENT:
Furaffinity.net:
NS1: NS23.WORLDNIC.COM 205.178.190.12
NS2: NS24.WORLDNIC.COM 206.188.198.12
NS3: UNASSIGNED
NS4: UNASSIGNED

FACDN.NET:
NS1: NS95.WORLDNIC.COM 205.178.190.48
NS2: NS96.WORLDNIC.COM 206.188.198.48
NS3: UNASSIGNED
NS4: UNASSIGNED

70.33.186.192-70.33.186.223:
InfoRelay Online Systems, Inc. INFORELAY-NETBLOCK03 (NET-70-33-160-0-1) 70.33.160.0 - 70.33.191.255
Ferrox Art, LLC FERROXART-01 (NET-70-33-186-192-1) 70.33.186.192 - 70.33.186.223

NetRange: 70.33.186.192 - 70.33.186.223
CIDR: 70.33.186.192/27
OriginAS: AS33597
Comment: http://www.inforelay.com - static allocation
RegDate: 2010-05-06
Updated: 2010-05-06 <--- Oh hey look, it hasn't been changed in over 3 years!

-- dig www.furaffinity.net --
;; QUESTION SECTION:
;www.furaffinity.net. IN A

;; ANSWER SECTION:
www.furaffinity.net. 4946 IN A 70.33.186.196

;; AUTHORITY SECTION:
furaffinity.net. 163218 IN NS ns24.worldnic.com.
furaffinity.net. 163218 IN NS ns23.worldnic.com.

-- dig www.facdn.net --
;; QUESTION SECTION:
;www.facdn.net. IN A

;; ANSWER SECTION:
www.facdn.net. 7200 IN A 70.33.186.221

;; AUTHORITY SECTION:
facdn.net. 171210 IN NS ns95.worldnic.com.
facdn.net. 171210 IN NS ns96.worldnic.com.

-- dig -x 70.33.186.196 --
;; QUESTION SECTION:
;196.186.33.70.in-addr.arpa. IN PTR

;; ANSWER SECTION:
196.186.33.70.in-addr.arpa. 3600 IN PTR www.furaffinity.net.

;; AUTHORITY SECTION:
186.33.70.in-addr.arpa. 86368 IN NS NS4.SITELUTIONS.COM.
186.33.70.in-addr.arpa. 86368 IN NS NS1.SITELUTIONS.COM.
186.33.70.in-addr.arpa. 86368 IN NS NS3.SITELUTIONS.COM.
186.33.70.in-addr.arpa. 86368 IN NS NS2.SITELUTIONS.COM.
186.33.70.in-addr.arpa. 86368 IN NS NS5.SITELUTIONS.COM.

-- dig -x 70.33.186.221 --
;; AUTHORITY SECTION:
facdn.net. 171811 IN NS ns96.worldnic.com.
facdn.net. 171811 IN NS ns95.worldnic.com.

;; QUESTION SECTION:
;221.186.33.70.in-addr.arpa. IN PTR

;; AUTHORITY SECTION:
186.33.70.in-addr.arpa. 3600 IN SOA ns1.sitelutions.com. reverse-dns.sitelutions.com. 233 28000 7200 604800 1

Oh, but that's not even the problem box - which has been explained in great detail by yours truly previously. The problem box is 66.231.180.84 which is a broken firewall/load balancer.

Ferrox Art, LLC FERROXART-02 (NET-66-231-180-80-1) 66.231.180.80 - 66.231.180.95
InfoRelay Online Systems, Inc. INFORELAY-NETBLOCK01 (NET-66-231-176-0-1) 66.231.176.0 - 66.231.191.255

NetRange: 66.231.180.80 - 66.231.180.95
CIDR: 66.231.180.80/28
OriginAS: AS33597
NetName: FERROXART-02
RegDate: 2010-05-06
Updated: 2011-09-24 <-- Would you look at that.. it's not updated either!

;; QUESTION SECTION:
;84.180.231.66.in-addr.arpa. IN PTR

;; AUTHORITY SECTION:
180.231.66.in-addr.arpa. 3600 IN SOA ns1.sitelutions.com. info.inforelay.com. 33 28000 7200 604800 1

If you were actually committed to resolving these issues, you'd quit making things up and actually do some basic troubleshooting. The kind that even level 1 tech support knows how to do. Instead of claiming it's the magical somehow impossible to comprehend "DNS" and making a bunch of hand-wavy motions to blame users.

Good luck on them paying heed. Acting on this would mean them accepting they were wrong and make them look bad. :P

You took the words right out of my mouth! I think I'm in love =P

ITT: FurAffinity staff pretend like they fix a problem

Still going on over here. Over a week now.

Took me 12 minutes to get that comment to post.

I'm still having major issues. I see this was posted the 20th... 22nd here. I'm having a very hard time connecting.

5:20 PM CT here in KY, and I'm still having problems with connecting to the site.

Well I don't like Twitter, its a pain to use, so I'm just going to post this here, besides, when I responded to the problem about the site not working every few minutes, I posted my trace and the creepiest thing happened, my ISP, Bright House just out of NO WHERE, pops up in the tweet to tell me they want to help. The hell, are they spying on me somehow? A bit creeped out o.O But here's a link to my text trace. https://www.dropbox.com/s/2ewzkeb11.....20Document.txt If you notice, one of them is WAY up there with 200ms while the first trace doesn't matter since it passed, yet it was the one having the issue. o.O Maybe I'm not seeing it right, I dunno. Either way, some weird stuff is going on.

Still getting it here but not as often.

Oddly enough, my connection has been perfectly fine via phone, on and off of wifi, and my laptop this past week.

After reading THIS, I've been having connection issues with the site...odd

I'm still unable to use FA, I get to click maybe two or three things and it says page cannot be found.

Still having issues with this via phone. Tried posting that from said phone and it just hangs on a page for 15 minutes.

According to my ISP Bright House Networks, they have spotted for me that it seems to be a Host Server problem. So yeah...

Still having issues on my laptop. But it's getting a little better.

I'm having horrid issues with FA lately, and it's not just my shitty computer. I've been trying on my phone to no avail. I'm lucky to get on right now...

Having issues -n- it sucks!

Definitely still getting the Time Out error issues. It's only been happening since the beginning of this week though so it's rather frustrating.

i'm still having issues with connections off and on. am i the only one or are others still having problems?

i've been getting error 504 gateway error time out either posting or replying to posts in general

We're still having connectivity issues in Colorado. My household has two members of the site on three connection platforms: Verizon Wireless 4G, T-Mobile 4G and Centurylink internet.

Like.. Everybody having issues is is Verizon, Bright House, or CenturyLink. Either these companies are purposely trying to strangle porn sites(somebody should browse some and see if they act up too. =x), or this firewall or whatever issue really hates these companies.

Issues connecting here as well.

It's still not working yet. It was starting to get a little better, then all of a sudden it gets even worse than it ever was.

Tracing route to furaffinity.net [70.33.186.196]over a maximum of 30 hops:
....
7 101 ms 102 ms 102 ms cr2-tengig-0-15-0-0.Washington.savvis.net [204.70.196.102]
8 113 ms 103 ms 104 ms msr1-tengig-0-3-0-0.Washington.savvis.net [204.70.196.98]
9 119 ms 102 ms 102 ms er1-gig-3-0-1.dck.savvis.net [204.70.203.6]
10 101 ms 101 ms 101 ms dca1.inforelay.net [208.173.12.130]
11 301 ms 207 ms 215 ms cr2.iad3.inforelay.net [67.208.76.5]
12 101 ms 104 ms 101 ms cr2.iad2.inforelay.net [67.208.89.118]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

I'm getting the exact same results my dear friend.

FA isn't that bad. At least, not until a week ago. Issue is unresolved. I just hope I am in one of the period where I am able to browse, when I hit, "Post".

its still glitchy for me.

Picturing some admin looking at a "Networking for Dummies" book with one hand while typing commands with the other...

It's hard to tell you I am having issues when I am unable to hit "post."