What NOT to do with no-ip :)
Posts: 486
My household will be swapping to a new ISP in near future for the reason of: its a better deal. But I've been told that they block port 80 incoming. So I did some pre-work and set up Apache2 to listen on 8080, modified routers, and in no-ip, I set that account to redirect to jenkins.hopto.org:8080. All went well with web server, no one seemed to complain, probably never even new difference.
But, I stopped getting external emails, and a friend of mine asked why my email server was down. I assummed that my current ISP started blocking port 25 incoming. So I found a site that probed and found 25 open on my end. Then the 8080 redirect hit me. Whenever someone sent mail to , it got redirected to :8080, which ain't good:)
So I changed Apache2 back to port 80, changed back routers, and no-ip will goto port whatever its told to.
What will I do when I swap ISP's and they block port 80? I am thinking of creating a new subdomain called mailjenkins.hopto.org and it will point to my broadband modem and jenkins.hopto.org will point to modem at port 8080. Only problem is my email address will change and thats always a hassle.
A lesson learned, thought I would share it.