Just a note. If you're requesting "telnet" or "ftp" access to your
'colocated' systems, the issue isn't only with your 'ISP'. I just got
finished assisting another MySQL user in rebuilding his system (for the 2nd or
3rd time) who has been using "telnet" and "ftp" to remotely administer his
systems (it appeared that the machine had been 'hacked', and once rebuilt,
they just watched for the new login password, and hacked it again).
Though the MySQL manual (and other README notes) makes it clear that you
should set a "root" password to protect your MySQL data from intruders, they
don't mention that you shouldn't 'broadcast' this info (or any other MySQL
user login info) over the Internet 'in the clear'. Why you would want any
hacker watching your network traffic to 'grab' your login name and password is
beyond me...
The issue of 'reverse DNS lookups' IS relevent if they (or you) are using any
kind of 'allow/deny' lists which will need to authenticate you before making a
decision on whether to grant or deny access. A lot of Internet Email systems
are now 'bouncing' mail that they recieve which they can't do a 'reverse
lookup' on the incoming IP to make sure it's really from who it says it is...
Gary Garrett wrote:
> We are also using AITCOM and often have problems. They seem to work on
> their network at noon on Sat. and traceroutes die at their network.They
> seem to go offline randomly also. We asked for telnet access to
> administer a Mysql database and can't get it to work. They say our DNS
> is not configured for reverse lookups...... what the hell our DNS has to
>
> do with their telnet I don't know. Their tech support is like M$oft,
> technically correct but has no relevance to the problem. You would be
> better served to learn Linux and see Rackspace.com for a dedicated
> Server you have full access to. Best bet is to find a NOC close to you
> in Internet space.
>
