Topic: Please Bear With Us

[FA Frey XC]

Everyone,

We're going through another forced change here at D.Net due to our ISP's incompetence.

Recently, Comcast switched to Time Warner in our area. Since I'm on a business class connection, they fubared it completely.

Bottom line is I've got to do a IP scope change, or renumber for those of you in the industry. This means from this Sunday to probably about Tuesday, connections will be spotty at best as the DNS changes propagate.

I'll post updates here as we move forward, I've already begun part of the switchover tonight by adding some new nameserver IP's at our registrar, that should trickle out by Sunday night and be fully propagated, then it's just a matter of changing my local DNS, and if I do it like I plan to, it should actually go quite smooth.

So, hang tight

I've got a reallly GOOD announcement coming after we get through this.

Regards,
~
Frey

[Commander Maxillius]

Gotcha, the rift interferes with all long range....


NUMBER ONE, EVASIVE....


(BOOM)

[FA Frey XC]

Everyone -

Tomorrow night is the night we'll have some bumpy-ness.

We're switching IP's then, and you should be good to go once we've updated the DNS.

Basically, you'll need to run the following command if you're running a Windows OS:

1.) Open a command line

2.) Type in the following:

ipconfig /flushdns

3.) Then type in the following :

ipconfig /registerdns

At this point, if you type in

ping frigga.xenocorp.net

and get a 70.89.9. XXX address with a request timed out, then your gonna have to wait an hour or so.

It should be relatively painless, as I've already propagated the Registrars ISP with the new DNS servers IP, that happened yesterday morning.

I'll post again here when we're done.

Regards,

Frey

[Corbomite]

Hey Frey,

I can't get PM's to go through. Is this part of the change over or do I need to do the above. If the latter, how do I open a "command line"?



"An Error Has Occurred!
fsockopen() [function.fsockopen]: unable to connect to frigga.xenocorp.net:25 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ) "

[FA Frey XC]

You get that error when the forums can't see the mailserver.

UPDATE:

I've gotten the IP changes done, and everything looks as it should. We should be 100% in about 24 hours, but as of now everything on our side is up and running.

Mail should be either working, or it will be working pretty soon, as it's 12:34am here and I'm still up tweaking, making sure everything is , indeed, working.

So, once I've confirmed mail flow, we should be good to go.

Regards,

[Rod ONeal]

Damn... Glad you're (we're) back up. I was coming down with DTs.

[Alphageek]

Everyone -

Tomorrow night is the night we'll have some bumpy-ness.

We're switching IP's then, and you should be good to go once we've updated the DNS.

Basically, you'll need to run the following command if you're running a Windows OS:

1.) Open a command line

2.) Type in the following:

ipconfig /flushdns

3.) Then type in the following :

ipconfig /registerdns

At this point, if you type in

ping frigga.xenocorp.net

and get a 70.89.9. XXX address with a request timed out, then your gonna have to wait an hour or so.

It should be relatively painless, as I've already propagated the Registrars ISP with the new DNS servers IP, that happened yesterday morning.

I'll post again here when we're done.

Regards,

Frey

Oh, sh*t,  really?  I'll never get that down.

[Corbomite]

You get that error when the forums can't see the mailserver.

An Error Has Occurred!
fsockopen() [function.fsockopen]: unable to connect to frigga.xenocorp.net:25 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. )


OK, cool, but I don't think all that swearing was necessary!   

[FA Frey XC]

Okay, everything should be working correctly, so we're just waiting for the last of the propagation.

I just re-sent the registration reminders, so hopefully we'll get a bunch of new members that can finally activate!

Regards,