TMZ hosting

Quote:

---

Originally Posted by dtkguy

Did you people having problems follow the instructions in the email that was sent out about re adding your addon domains, etc? It seems you're all down since the crash date. I was too, but upon getting the instructions in email, I've been back online since the late 22nd or early 23rd.

---

I tried to, and it spit out an error every time I try to re-add my add-on domains.

There was a problem creating the addondomain. Show Details

Error from park wrapper: Using nameservers with the following IPs:
66.37.153.109,66.37.153.100 Sorry, the domain is already pointed to an
IP address that does not appear to use DNS servers associated with this
server. Please transfer the domain to this servers nameservers or have
your administrator add one of its nameservers to /etc/ips.remotedns and
make the proper A entries on that remote nameserver.

I wrote support about the issue and they wrote me back asking for my username, password, and domain name.

Ordinarily I am a patient person, but being asked for my username and password sent me over the edge. I know it's a small thing, but as a customer I just feel like they should know who I am and as an ex security goon I've been trained to never give my password to support personnel.

My patience for dealing with troubles from TMZ completely ran out. I'm taking a few days to let my temper cool down so I can make rational decisions regarding proxy hosting.

Quote:

---

Originally Posted by Will.Spencer

I tried to, and it spit out an error every time I try to re-add my add-on domains.

There was a problem creating the addondomain. Show Details

Error from park wrapper: Using nameservers with the following IPs:
66.37.153.109,66.37.153.100 Sorry, the domain is already pointed to an
IP address that does not appear to use DNS servers associated with this
server. Please transfer the domain to this servers nameservers or have
your administrator add one of its nameservers to /etc/ips.remotedns and
make the proper A entries on that remote nameserver.

I wrote support about the issue and they wrote me back asking for my username, password, and domain name.

Ordinarily I am a patient person, but being asked for my username and password sent me over the edge. I know it's a small thing, but as a customer I just feel like they should know who I am and as an ex security goon I've been trained to never give my password to support personnel.

My patience for dealing with troubles from TMZ completely ran out. I'm taking a few days to let my temper cool down so I can make rational decisions regarding proxy hosting.

---

I understand your problem, but asking for the password is nothing too bad. My host does it too. There's no way (that I know of) to get access to a user's account without either using their password, or changing it. And asking for it is the better option.

Just change your password, give it, and then change it back.

Quote:

---

Originally Posted by Will.Spencer

I tried to, and it spit out an error every time I try to re-add my add-on domains.

There was a problem creating the addondomain. Show Details

Error from park wrapper: Using nameservers with the following IPs:
66.37.153.109,66.37.153.100 Sorry, the domain is already pointed to an
IP address that does not appear to use DNS servers associated with this
server. Please transfer the domain to this servers nameservers or have
your administrator add one of its nameservers to /etc/ips.remotedns and
make the proper A entries on that remote nameserver.

I wrote support about the issue and they wrote me back asking for my username, password, and domain name.

Ordinarily I am a patient person, but being asked for my username and password sent me over the edge. I know it's a small thing, but as a customer I just feel like they should know who I am and as an ex security goon I've been trained to never give my password to support personnel.

My patience for dealing with troubles from TMZ completely ran out. I'm taking a few days to let my temper cool down so I can make rational decisions regarding proxy hosting.

---

Ahh yeah, that's a pain in the ass right there. One for cPanel being tied to having addons pointed to itself in the first place and Two for them wanting your user/pass when they could easily fix this without any need to enter your cPanel account at all. I mean isn't this something that can be fixed via an admin interface or direct access to the server? Them in your cPanel isn't going to make it magically accept your domains with custom nameservers.

If everyone gave the details we asked for then all the problems would be solved much faster. Will I am not seeing a ticket from you, but that error you are receiving is very easy to fix if you give all the information we ask for. If your websites are NOT working just open a ticket stating that its not working and we will get that taken care of.

- Daniel :)