Well, in all the years that I used to play with ms's sql,
we always used port numbers and then connected with odbc. With that in mind, you
could basically do the same thing in this case. If you wanted someone to be able
to connect, retrieve, write, delete records in a MySQL data base that you are
hosting, it would seem to me that it would be better to do it that
way.
Having your SQL server advertised as a sub domain might
could be a big security risk because it would then be published as if it were a
web site and that would allow people to start cracking on it till it
breaks.
If you use something like 123.123.123.123:3310 and you have
it set up through a VPN to the other sites that you want connection to, then
that would provide a ton more security.
Doug
oh awesome, i thought using a records as i've seen in the past places
doing that like
dreamhost.com etc. Is this
port better security or something ? what is this actually called
?
cheers, rob
On Sat, Jun 21, 2008 at 9:17 AM, Doug Harvey <
ohgoodiee@gmail.com> wrote:
Rob. I
would think that you would want to use a port number instead of a domain
name. I think the port number is 3310, so you would have someone connect
by going to: domainname.com:3310
Doug
Hey there,
wondering if some one could point me on the right
direction. I have no idea what its actually called but i want to asign my
MYSQL to a domain name.
So instead of using local host they can use
mysql.domainname.com
Basically want this to make my database accessible to our other
servers which are hosted at all diffrent places around the world.
Could
any one give me a brief idea on how this is done ? and the pro's and cons of
it.
I did trying searching for it but seams i dont actually know whats
its properly called i came up with very little. I thinking this is done in
apache ? im just guessing
here
thanks,
rob