Ok, after almost a month of not being able to play on my favorite NS server I've done a little research.
I did a trace on the server's IP (72.35.235.130). The trace showed me that the following network is blocking my connection:
gig-1-3.core-02.lax.ip.net1one.com (72.35.230.214)
I am able to connect from work and a trace from work shows that this network is one hop away from the jigglypuff server.
tfc.panduck.com resolves to ip: 72.35.235.131, so the website is on a different IP than the NS server. What's strange is that the gig-1-3.core-02.lax.ip.net1one.com (72.35.230.214) network allows me to connect to 72.35.235.131 (the website), but not 72.35.235.130 (the NS server).
And again this all happened after my cox at home subnet changed from 68.7.*.* to 72.199.*.*
Furthmore I have looked up the contact information for the gig-1-3.core-02.lax.ip.net1one.com (72.35.230.214) network and came up with the following:
-----------------------------------------------------------
OrgName: FUZION COLO
OrgID: FUZIO-1
Address: 701 GreenValley Pkwy
Address: STE 200
City: Henderson
StateProv: NV
PostalCode: 89074
Country: US
ReferralServer:
rwhois://rwhois.fuzioncolo.com:4321
NetRange: 72.35.224.0 - 72.35.239.255
CIDR: 72.35.224.0/20
NetName: FUZION-COLO-BLK-III
NetHandle: NET-72-35-224-0-1
Parent: NET-72-0-0-0-0
NetType: Direct Allocation
NameServer: NS1.FUZIONCOLO.COM
NameServer: NS2.FUZIONCOLO.COM
Comment:
RegDate: 2005-04-29
Updated: 2007-10-26
RAbuseHandle: TECHN183-ARIN
RAbuseName: Technical
RAbusePhone: +1-877-838-9466
RAbuseEmail:
abuse@fuzioncolo.com
RNOCHandle: TECHN183-ARIN
RNOCName: Technical
RNOCPhone: +1-877-838-9466
RNOCEmail:
abuse@fuzioncolo.com
RTechHandle: TECHN183-ARIN
RTechName: Technical
RTechPhone: +1-877-838-9466
RTechEmail:
abuse@fuzioncolo.com
OrgTechHandle: TECHN183-ARIN
OrgTechName: Technical
OrgTechPhone: +1-877-838-9466
OrgTechEmail:
abuse@fuzioncolo.com
-----------------------------------------------------------
I called their tech support line and was on hold for 45 minutes (in "position 1" in their queue) and no one ever answered.
My guess is that there is some sort of security concern that is enforced in the network that is blocking my connection and since I can connect from work my guess is that they do not want people connecting to the NS server's IP from cox at home accounts, strange...
Thoth, please forward this information to Jigglypuff and see if this helps him diagnose the problem, thanks!