Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I understand the basics of DNS i just have what i hope to be a quick and painless question.
I have a domain through godaddy. Such as www.mydomain.com. I have my webserver set up. I want to start hosting other companies/peoples webpages for them. I understand that my isp (Comcast) blocks smtp. Obviously i would want my customers to have email at there domain. ex. www.mycustomer1.com
If i get the DynDns(www.dyn.com) service here how do i set it up? Also would i be able to use that for email as well. I have comcast and they will block my smtp ports. Or will i have to buy the email service from Dyn as well?
If i need to get DynDns and DynEmail for email to work than it just makes sense money wise to get comcast buisness class?? Right?
When I visited their site, I saw that have a video on email, for example.
I used to use No-ip.com when I had Comcast. I wasn't concerned with the email, but, at least then, Comcast was not blocking port 80 (though they did block port 25), so I could self-host my website in that way. The way it worked was that, after registering, I installed a small program on my server and set it to start at boot. It would periodically (every few minutes or so) contact no-ip.com; that kept their record of my IP address up-to-date. Dyn seems to work in much the same way.
You can often get around port 25 blocking by using another port, such as 462 (Comcast improperly blocked me for spamming--when I called support, they told me to just use 462.)
+1 on dyn.com. I have been a customer of theirs for several years. The service has been 100% reliable and the support has been excellent. I no longer use their dynamic service, but I do use some of their other services, such as my domain registrar.
You would be better off doing this from a VPS or hosted location. Using a consumer line to host websites does violate your ToS with Comcast. Plus you really do not have an SLA for repair/response to trouble issues.
You would be better off doing this from a VPS or hosted location. Using a consumer line to host websites does violate your ToS with Comcast. Plus you really do not have an SLA for repair/response to trouble issues.
From what I can tell from scanning for the relevant portions, you are free to host a webserver, but not for commercial purposes. Grim76 is correct, your desired application would be better off hosted somewhere else, or perhaps upgrade to a different (business) service. As I mentioned in my previous post, I no longer use Dyn's dynamic service. The reason being is that I now use business grade service which does not have the dynamic IP limitations.
I ultimately stopped self-hosting because my WordPress database became too large for the P4 I was using as a server--it ran, but required frequent maintenance--plus I moved to a location where the cable company was much more hostile than Comcast. Their terms of service say, "no servers."
Self-hosting is first a challenge, then a great learning experience, then a headache (grin). If the terms are service are no danger, I'd say go for it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.