Dang, I've having trouble signing on since early this morning... I was going through withdrawal.... *shakes and shivers*

I've been having touble too

bmwracer wrote:

Dang, I've having trouble signing on since early this morning... I was going through withdrawal.... *shakes and shivers*

Yeah. I had some hard times too. See what happens when Genma goes to France leaving this place unattended!
_________________

ahochaude wrote:

Yeah. I had some hard times too. See what happens when Genma goes to France leaving this place unattended!

Yep. Like I said: the place is going to be a shambles....

I didn't notice......


Anyways, I wasn't on yesterday so yeah.

The cause of the downage was due to both NS1 and NS2 DNS servers being down at JDorama.com's ISP. If your ISP cached the IP address at their DNS server, more likely you didn't have a problem connecting. However, other ISPs who refreshed their DNS after NS1 and NS2 shutting down wasn't able to connect.

I researched it for about 1 hour earlier today...

--- groink

I guess the server being down is still having it's after effects.

So damn slow. No one is here.
_________________

If you're geeky enough (and can actually read this), you can fix your PC to surf JDorama.com, or avoid a DNS server re-fresh:

1) Go to Start | Run...

2) Type in "notepad %windir%\system32\drivers\etc\hosts" then click OK.

3) On the very bottom (right underneath 127.0.0.1 localhost), add:

207.44.218.55 jdorama.com
207.44.218.55 www.jdorama.com

then save the hosts document. For operating systems other than Windows, just locate your hosts file (*nix and even Mac OS X has this) and make the exact same change.

Even if you can surf JDorama.com right now, your ISP's DNS may eventually re-fresh, dropping JDorama.com if NS1 and NS2 are still down.

However, if after a few days of putting those two lines in you can no longer surf JDorama.com, remove both of those lines, save hosts, then try again. This is in case the ISP does actually change the IP address of the JDorama.com site.

--- groink

groink wrote:

If you're geeky enough (and can actually read this)

I could post a zone file

I'm guessing not too many people can access this site now. If they can, they might want to try your workaround because their DNS cache may time out.

It's strange, jdorama's primary nameserver seems dead, and the secondary is up, but seems to have forgotten about jdorama.com. That's nutty

I dunno if it'll help, but I wrote a note to jdorama.com's technical contact to let them know about the problem.

Trying to move the technical issues along, I right now have technical support for hostingdepartment.com in chat mode (they own popularsitehosting.com, who hosts jdorama.com's domain name on their DNS servers). Here's the actual stream:

David:Hello! Welcome to HostDepartment Live Chat Service. How may I help you?

groink:hi! i'm trying to help out a friend who's jdorama.com is being hosted on popularsitehosting.com

groink:the site still works, however ns1.popularsitehosting.com isn't resolving it

David:Yes Sir.. It is being propagation since it has new IP.

groink:his site is still 207.44.218.55 (at least it's working)

groink:so i can't see why the need for propogation

groink:is ns2 also running through the same process?

groink:i can nslookup on ns2, however it's like jdorama.com was forgotten by it

groink:i can't even nslookup on ns1

David:Yes Sir.. since it is being propagation..

groink:i don't understand though... i can understand that my local DNS wouldn't have it as a result of propagation. However, wouldn't NS2.popularsitehosting.com at least have a copy of it? if it doesn't, isn't all the DNS's all over the world also loosing jdorama.com?

groink:in theory, ns2 should be the backup for ns1, and all the DNS' on the 'net should be propagating off of NS2

groink:that's why I tend to believe that jdorama.com is simply missing from the DNS database on that server

***** about a 5 minute pause *****

and then I just closed the chat window. This is purely stupid and very un-professional on their part! First off, jdorama.com is still at the same IP address as before (207.44.218.55). So there is no reason for propagation on that level. Second, I think when he mentioned propagation, he probably meant that the IP address for ns1 has been changed. However, it appears that ns2 isn't that reliable of a backup DNS, as vibius pointed out earlier.

JUST RIGHT NOW, even ns2 is now down, therefore there is NO DNS on popularsitehosting.com now. I think after what I told the tech about ns2, they must've found a major problem with it.

What a total mess! As a result, we're looking at AT LEAST 72 hours for propagation to update the entire 'net. And that's if they fixed it RIGHT NOW! If they delay it further, the 72 hours is also going to be delayed. What a bozo moron operation!

--- groink

groink wrote:

Trying to move the technical issues along, I right now have technical support for hostingdepartment.com in chat mode

Ah, thanks for looking into this, I wrote them an email ... but ...

Quote:

David:Yes Sir.. since it is being propagation...

This sounds like droidspeak for: "Duh, wh-what???" It's their own darn nameservers, they can reload the zones any time of day.

Quote:

What a total mess! As a result, we're looking at AT LEAST 72 hours for propagation to update the entire 'net. And that's if they fixed it RIGHT NOW! If they delay it further, the 72 hours is also going to be delayed.

If they are changing the IP, then I believe propagation would only depend on what the previous TTL was ... which I don't know because the DNS has entirely evaporated. (I think we can assume it has expired anyway, since no one is logged in). But if the IP remains the same, I suspect that as soon as they start serving the correct DNS, users will get back on immediately.

Quote:

What a bozo moron operation!

Apparently.

The fix for this is trivial ... they just need to get their DNS guy on it, assuming he has a braincell.

Too bad one of us isn't listed as a technical contact for the domain, we could set up a new secondary and get people back to their beloved jdorama surfing!

It would probably be a good idea to at least get one new nameserver outside of this podunk ISP. soa.granitecanyon.com offers free secondary DNS service ... for one.

I gotta wonder what (un)popularsitehosting.com is up to. All day long I can't even resolve their own domain (which uses the same nameservers as jdorama). So I guess they aren't getting any email complaints.

Maybe they can't even log into their own nameservers to fix the problem because they fudged up their own DNS.

That would be funny as hell. Except of course for the collateral damage we are seeing.

<hr width="80%">
Edit: I see groink posted more info at d-addicts:

http://www.d-addicts.com/forum/viewtopic.php?t=2300

I can't believe they screwed things up for so long. It's not that hard to move a site in DNS with zero down-time. It just takes a little forethought.

vibius wrote:

I dunno if it'll help, but I wrote a note to jdorama.com's technical contact to let them know about the problem.

Oops it looks like the listed address has expired ... so I think I may have found a better one. I'll see if it works. Maybe the technical contact can get this fixed.

I can't believe the ISP has let the problem go on so long.

deng i didnt even have the whole access here yesterday and i was soooo bored and ended up posting on the other forums i go to
_________________

Well, welcome back. But I think it may be a while before the problem is fixed and jdorama is back to normal.

vibius wrote:

Well, welcome back. But I think it may be a while before the problem is fixed and jdorama is back to normal.

Yes... Peforming a nslookup on my Road Runner DNS', still no zone entry for jdorama.com. However, looks like ns1 is back up, so that's probably slowly bringing in more people.

--- groink

yeh, bmw just emailed me that he still couldnt access
_________________

MixxDreamer wrote:

yeh, bmw just emailed me that he still couldnt access

Probably due to DNS caching ... I restarted my nameserver recently and I'm seeing that jdorama.com is now resolving correctly to it's IP address. So everyone should start seeing the correct address soon and be able to access. It may just take some folks a little longer than others.

Just a short time ago, I was having a problem because the jdorama web server was hanging. It looked like a packet loss problem ... but maybe it's over now.

I hope it all stays fixed!

Whoa I couldn't access this site all weekend... Friday night was the last time I got in
_________________