old MSP won't give up domain name
-
@Dashrender said in old MSP won't give up domain name:
@scottalanmiller said in old MSP won't give up domain name:
@Dashrender said in old MSP won't give up domain name:
@momurda said in old MSP won't give up domain name:
Not actually stealing domain name, at least not yet since it was renewed through old msp recently. Still unacceptable. Still dont know why the owner is handing this off. Probably because he cant do anything for himself and is used to having other people wipe his own ass. My point about disrupting them is still valid. The owner should be handling this. Not an IT guy. It really sounds like the owner doesnt actually give a shit, or not enough to do something himself. Which means @Mike-Davis shouldnt either, but probably does because of professional pride.
This is definitely a glass tower type is position you have. Not saying it's entirely wrong, but geez, how many people know that they should maintain their own domain name registration? If you're not IT, probably not many.
Here's where I sit back and allow Scott to provide a list of things that fall through the cracks just like this.
of courseThis isn't anything IT. How many people know to get a real estate agent and a deed when buying physical property? If we were having this same discussion about other items of ownership we'd never have this "socially accepted incompetence" idea. What makes this singular non-technical item unique? Why would the CEO think that something like a real estate deed or his incorporation papers should be handled by a random outsourced?
What's random about it? The use of a domain name is entirely IT. Notice I said use. I'm with Mike when I say that I wouldn't expect any business manager to know that they are the ones who should hold the registrar information. Because of it's technical nature - it appears that it belongs in the hands of IT - I see now through this conversation (and past ones) why it's not, but why should they see it your way? The CEO's job is to decide that they need one, and what it will be, the acquisition seems understandable to be the job of IT.
Of course purchasing and maintaining a domain name is the job of the IT department. But it is not the IT department's job to try to recover something that they did not control in the first place. A proper way this should've been handled was it would've been registered in the company name to a company email address The fact that this was signed off not registered to the company is a failure of whoever signed it off in this case the CEO
-
Actually Scott disagreed with you above... He said it was the CEO or business manager job to acquire it. They then would have the credentials to recover if needed.
-
The CEO isn't trying to "pass the buck". I told him what I needed, did my best to explain the difference between a website and a domain, etc. Then I helped him write an email to the old MSP saying he would like the Auth Code so he can transfer the domain. At that point the old MSP stopped communicating. The CEO asked what to do next, so I helped him write an email to bluehost.
If you don't call an IT guy to do a whois lookup so you can find out where your domain is registered, who do you call?
At this point I told him that from bluehost's last response it looks like he might have to contact his laywer.
-
@Dashrender said in old MSP won't give up domain name:
Actually Scott disagreed with you above... He said it was the CEO or business manager job to acquire it. They then would have the credentials to recover if needed.
No Scott is saying the CEO specific to this instance. Because for this instance the business is the CEO there is nobody else.
The CEO outsourced IT. This was actually a good choice. The CEO did not delegate somebody to manage and verify their outsourced work. This was a bad choice.
-
@Dashrender said in old MSP won't give up domain name:
@scottalanmiller said in old MSP won't give up domain name:
@Dashrender said in old MSP won't give up domain name:
@momurda said in old MSP won't give up domain name:
Not actually stealing domain name, at least not yet since it was renewed through old msp recently. Still unacceptable. Still dont know why the owner is handing this off. Probably because he cant do anything for himself and is used to having other people wipe his own ass. My point about disrupting them is still valid. The owner should be handling this. Not an IT guy. It really sounds like the owner doesnt actually give a shit, or not enough to do something himself. Which means @Mike-Davis shouldnt either, but probably does because of professional pride.
This is definitely a glass tower type is position you have. Not saying it's entirely wrong, but geez, how many people know that they should maintain their own domain name registration? If you're not IT, probably not many.
Here's where I sit back and allow Scott to provide a list of things that fall through the cracks just like this.
of courseThis isn't anything IT. How many people know to get a real estate agent and a deed when buying physical property? If we were having this same discussion about other items of ownership we'd never have this "socially accepted incompetence" idea. What makes this singular non-technical item unique? Why would the CEO think that something like a real estate deed or his incorporation papers should be handled by a random outsourced?
What's random about it? The use of a domain name is entirely IT. Notice I said use. I'm with Mike when I say that I wouldn't expect any business manager to know that they are the ones who should hold the registrar information. Because of it's technical nature - it appears that it belongs in the hands of IT - I see now through this conversation (and past ones) why it's not, but why should they see it your way? The CEO's job is to decide that they need one, and what it will be, the acquisition seems understandable to be the job of IT.
Use of a building is completely maintenance. But the maintenance people don't get paid to buy your real estate. It's not technical in nature. It's an identity purchase. Setting the dns after you buy it now that is technical. But not buying a name. Acquisition of a domain should never go to IT and you can see here exactly why.
-
There you go JB, right from the horse's mouth.
-
@JaredBusch said in old MSP won't give up domain name:
@Dashrender said in old MSP won't give up domain name:
Actually Scott disagreed with you above... He said it was the CEO or business manager job to acquire it. They then would have the credentials to recover if needed.
No Scott is saying the CEO specific to this instance. Because for this instance the business is the CEO there is nobody else.
The CEO outsourced IT. This was actually a good choice. The CEO did not delegate somebody to manage and verify their outsourced work. This was a bad choice.
That would work too. Someone on the business team needs to take ownership of critical business stuff. IT can assist or push the buttons or advise. But the account and final control can't be passed off somewhere.
-
@Dashrender said in old MSP won't give up domain name:
There you go JB, right from the horse's mouth.
Whether or not purchasing a domain is IT was not what I was discussing I was discussing's got you some claiming it was all CEO and nothing else.
It is the business, not the CEO but in the case of this instance the CEO is the business
-
This cannot be good for business. Because in this situation you are either billing for legal hours when you have no legal credentials or you are working for free.
-
@IRJ said in old MSP won't give up domain name:
This cannot be good for business. Because in this situation you are either billing for legal hours when you have no legal credentials or you are working for free.
Based on @Mike-Davis last response, he gave advice based on past experience and said you probably need a lawyer to go farther. So it does not sound like he did anything wrong or for free.
-
@JaredBusch said in old MSP won't give up domain name:
@Dashrender said in old MSP won't give up domain name:
There you go JB, right from the horse's mouth.
Whether or not purchasing a domain is IT was not what I was discussing I was discussing's got you some claiming it was all CEO and nothing else.
It is the business, not the CEO but in the case of this instance the CEO is the business
Right. Likely all one here.
-
@JaredBusch said in old MSP won't give up domain name:
@IRJ said in old MSP won't give up domain name:
This cannot be good for business. Because in this situation you are either billing for legal hours when you have no legal credentials or you are working for free.
Based on @Mike-Davis last response, he gave advice based on past experience and said you probably need a lawyer to go farther. So it does not sound like he did anything wrong or for free.
Yeah seems like they are on the right track now.
-
Don't think that there is much more to add here. Fill the owner in on the deets, let him decide now to proceed.
