I haven't been to bizarro world recently, but I don't think the problem is fixed.
I did a whois on jpfitness.com and jpfitness.org and looked at the responses I get back from dig talking directly to your DNS servers, so my local caching should be a non-issue.
This is what I found:
NS1.FVGWEB.COM says
forums.jpfitness.com. 3600 IN A 67.18.213.26
NS2.FVGWEB.COM says
forums.jpfitness.com. 5 IN A 74.53.227.146
NS383.WEBSITEWELCOME.COM says
forums.jpfitness.org. 14400 IN A 67.18.213.26
NS383.WEBSITEWELCOME.COM says
forums.jpfitness.org. 14400 IN A 67.18.213.26
Also FWIW, the websitewelcome.com DNS servers say (authoritatively) .com is at 74.53.227.146, but since those aren't listed in the whois record for jpfitness.com no one should be querying those. The only people affected by that are, presumably, people waiting for the site to propagate... and they would always go to the old site.
To summarize, the problem is that the primary and secondary DNS servers listed in the jpfitness.com whois entry do not agree. I think the secondary is wrong, but I don't know for sure. You and/or your guys ought to be able to tell.
I hope that helps some.