The only way to hide the port number is to have the client connect on the default port (port 80). If you are listening for a connection on port 3232, and the client doesn't have that in the URL, how would it know to connect on that port? Just basic TCP issues.

Sorry, this is frankly ridiculous now. youjust keep asking the same question again and again, which i assure we we absolutely do understand. you clearly do NOT understand IP or you would have realised we are right a long long time ago. so why not just take our advice or live with what you've currently got. what you want is not going to happen.

I know that http uses port 80 just like ftp uses 21. I understand that you believe that the only way to hide the port number is to use the default port 80. If I ask apache to listen on a different port I know that I have to add the port manually to get to that destination. That is why I have to add port 3232 after my address. Maybe I should rewrite my question and just say... how does my DNS provider supply a service that allows my browser to show that I am at http://www.mysite.com when actually I am at http://www.mysite.com:3232. I think that will make more sense to the both of you them the way I am currently asking my question.

Your DNS provider runs a webserver on their system at mysite.com and forwards the incoming request to <yourip>:3232. Effectively, it's a reverse transparent proxy.

yes but can he just not use mod_rewrite on apache to remove the :3232 part of the url? ;-)