Hi guys, i was testing on my client domain. I can't ftp in using ftp.myclientdomain.com but can use www.myclientdomain.com or myclientdomain.com to ftp in. Why is it so weird? What settling did i do wrong on my raq?

Did you setup an A record for ftp.myclientdomain.com in DNS?

If you haven't done this, the name ftp.myclientdomain.com will not resolve and you will not be able to ftp using this domain name.

Cheers
Mark

i did not...ok. thanks..i thought i need to add A record for domain.com and www.domain.com only..
but my mainsite doesn't have ftp.mymainsite.com in dns.. and still work..so weird

ftp. whatever is just a host name signifying that the machine is/has ftp on it. You could name a machine bill and still have ftp running on it. a hostname + domain name is what makes up a fully qualified domain name or FQDN. Generally what we do for our clients is make a cname for all of those popular host names ftp, www, mail, smtp, etc so folks don't get to confused. HTH.

Originally posted by kaz
only.. my mainsite doesn't have ftp.mymainsite.com in dns.. and still work..so weird
Hmm... That is indeed wierd. Are the DNS entries for your mainsite actually in your own DNS?
If they are being resolved by your co-lo then they might have ftp.... set-up for you without you knowing.

Cheers
Mark

Or just wildcard the domain. This way, anything.domain.com will hit the server and as far as mail and ftp is concerned, the name doesn't much matter so long as it hits the server.