NameCheap: Configure domain name to point to the server itself [mx record] [ip]

Q: How can I change my domain to an port with a # (233.23.12.34:124) and my e-mail () or whatever to the same point to a different port #. I want my whole server to handle everything on my domain. I just want to play around with it for a while.

Any suggestions?


Re:here is how i do the http stuff – i first sign up for a free dns redirection from no-.com, say http://xxx.no-.com, select it and then install their auto update client so that no- always has my current WAN and anything going to http://xxx.no-.com comes to my machine. then i go to godaddy.com and buy the "real" domain name i want, say www.xxx.com or whatever. godaddy.com has a forwarding section and in there i tell it to forward www.xxx.com to http://xxx.no-.com:7255, the last part being the port number since port 80 is blocked. just make sure you LAN machine has a static and you forward port 7255 to the correct LAN machine, all done with http.

the problem is that it is not easy to redirect the mail, so no-.com has a mail redirector where your mail goes to them, and then gets redirected to whatever port you make your mail server receive mail on. the problem is i think it is ~$40/year so it would probably be cheaper to get in on one of these $25/year website deal, if they have what you need.

i started doing this years ago before they were blocking 80 and 25, so now i have a couple domains pointing to my home that do not get email, they would just be websites and then i have one website that i pay yearly for basically just so i have a email address that is not bob32432@cox.net or whatever.

no- or any of the free dns forwarding providers are great for ftp, non-professional websites that can have a name like http://bob.sytes.net, or easy to remember game servers and such, but until they unblock 25 it is probably cheaper to go with a "real" webserver…


Re:I think dyndns offers port redirection stuff, but using nonstandard ports is evil.

Re:I dont mind paying for it. I just dont want to pay $$$ a month for it. I might as well get a colocation server.

Re:Originally posted by: guy
My ISP blocks port 80 and 25.

when i get back from the dr i will tell you how to do it for port 80, but for port 25 there is no easy(free) workaround


Re:My ISP blocks port 80 and 25.

Re:Send the domain to the same , and use port forwarding on a router to send the the correct area.

Re:I'm 99% sure you can't do that. It's not how dns works. Port is determined by the application. For ex, your web browser, by default will attempt to connect to port 80. It doesn't take a port argument from DNS.

Also, I can't imagine any possible reason why you'd want to do it that way.


Re:I don't know if it's possible to specify a port with DNS. NameCheap does have really good documentation though… this (http://namecheap.simplekb.com/kb.aspx?show=article&articleid=32&categoryid=0) (URL redirect) might be helpful for web serving, but probably not for MX.

Related posts

Leave a comment

0 Comments.

Leave a Reply


click to changeSecurity Code

[ Ctrl + Enter ]