Everything was scheduled to move on wednesday Nov. 3rd, 2004. That changed as of Yesterday. The DSL provider decided it could not give me the same service I have currently. The best thing they could give me was iDSL or 144Kbit/sec service at twice the cost I am currently paying.Now the Good news:
I asked WTFH. They said *SOMEHOW* the loop length changed from 7,000 feet to 19,350 feet. Which qualified for HDSLv2 @ 768K, but since the DSLAM that services my area is older... it cannot do HDSLv2.
My only other option was to go with a T1 service. DAM DAM DAM DAM DAM.
9-10 days is the soonest they can get it in place. Well.
New T1 and a NOT MCI connected bandwidth provider == New IP Addrs. DAM DAM DAM DAM DAM.
We are getting an better service (faster supposedly). A dedicated T1 and we are getting New IP Addresses.! YEAH!
Okay, what this means is that knight.gregfolkert.net (the machine's real name) will be up and running until I can transfer it to the new locale. When that happens EVERYTHING hosted on it will have to change the ROOT DNS server information. That means for DNS I host affected domains are as follows:
gregfolkert.[ net | com | org ]
chapman-anderson.org
dkime.com
fortwhitetail[ | ranch ].com
iwethey.org
keo-usa.com
mr-anderson.net
bethanneweiland.com
And those having pointing stuff at knight for apache and other hosting will have to change where they pointing to (if I also host DNS, don't worry I fix the zone files proper), affected names is as follows:
*.gregfolkert.[ net | com | org ]Currently I do not have IP Addresses to give out, but when I get them I will let you know. And I will announce here and e-mail the affected parties.
*.fortwhitetail[ | ranch ].com
*.dkime.com
*.iwethey.org
*.keo-usa.com
*.hope-ride.[ org | com | net ]
*.chapman-anderson.org
*.mr-anderson.net
*.bethanneweiland.com
Gads I hate it when things go awry.
BTW the new firewall, is a machine I built doing everything wrong (according to the Debian Installer team), but it works just fine has redundancy and all that built right in.