IRC and Stardock?

 I have Cox Cable as my ISP and I cannot connect to irc.stardock.com for some reason (google it and others have had this problem).  Is there any known work around for this yet? 

4,015 views 7 replies
Reply #1 Top

I've never been able to connect to Stardock's IRC either (from within Demigod via the overlay, within Impulse, or using an external IRC client). Now I know why. I have Cox as well. It seems strange to me that Cox would block its customers from it (well according to what I found after googling the issue that is the case).

Reply #2 Top

It didn't used to. I signed on when demigod was first announced, then it couldn't connect later, though I can connect to other locations just fine.

Reply #3 Top

ah, I opened a ticket with support about this, but I am also on Cox so I guess there will be no work around

Reply #4 Top

https://forums.stardock.com/326700

 

Cox is apparently changing the DNS record, add the following to /etc/hosts (In windows, located in C:\windows\system32\drivers\etc\hosts)

38.98.152.138    irc.stardock.com

 

Or use alternative DNS servers. (In the past I've used OpenNIC, for other reasons. I'm sure there's more than just that out there.)

Reply #5 Top

Quoting The_Deathstalker, reply 4
https://forums.stardock.com/326700

 

Cox is apparently changing the DNS record, add the following to /etc/hosts (In windows, located in C:\windows\system32\drivers\etc\hosts)

38.98.152.138    irc.stardock.com

 

Or use alternative DNS servers. (In the past I've used OpenNIC, for other reasons. I'm sure there's more than just that out there.)
End of The_Deathstalker's quote

 

I don't think that would work. I've tried to connect to irc.stardock.com directly by typing in its ip address rather than its url and it still doesn't work.

Reply #6 Top

Does for me. So Cox may be actually blocking in your area.

 

Make sure you are using the one above and *not* what Cox's DNS reports, which is incorrect.

Reply #7 Top

Quoting The_Deathstalker, reply 6
Does for me. So Cox may be actually blocking in your area.

 

Make sure you are using the one above and *not* what Cox's DNS reports, which is incorrect.
End of The_Deathstalker's quote

 

Yeah I think Cox is actually blocking it. When I try 38.98.152.138 I just get:

Bad Request (Invalid Hostname)