Ok slow down Mr. Adventureran.
I just tried your subdomain from three connections, ran tracerts from three connections and they are all locating and displaying your subdomain just fine.
Here are the results of my testing. Afterwards I come to the conclusion that this is NOT on our end.
Server: DNS server ns4.coastlandtech.com
aaron.ransplace.com internet address = 66.246.85.77
ransplace.com nameserver = ns1.totalchoicehosting.com
ransplace.com nameserver = ns2.totalchoicehosting.com
ns1.totalchoicehosting.com internet address = 64.246.50.105
ns2.totalchoicehosting.com internet address = 65.254.32.122
-----------------------------------
Server: DNS server ns4.coastlandtech.com
Non-authoritative answer:
ransplace.com nameserver = ns1.totalchoicehosting.com
ransplace.com nameserver = ns2.totalchoicehosting.com
ransplace.com
origin = ns1.totalchoicehosting.com
serial = 1051321856
refresh = 28800 (8H)
retry = 7200 (2H)
expire = 3600000 (5w6d16h)
minimum ttl = 86400 (1D)
Authoritative answers can be found from:
ransplace.com nameserver = ns1.totalchoicehosting.com
ransplace.com nameserver = ns2.totalchoicehosting.com
ns1.totalchoicehosting.com internet address = 64.246.50.105
ns2.totalchoicehosting.com internet address = 65.254.32.122
-------------------------------
Also - I ran digs on your subdomain and they were all fine.
The only thing I see that you have done wrong, is when your account was upgraded to reseller you didnt change the Nameservers. This might effect this issue, but I doubt it.
You should update your Nameservers to
NS1.TOTALCHOICEHOSTING.COM and NS2.TOTALCHOICEHOSTING.COM
Further please provide more detailed information. It helps me trace down problems.