Viewing a response to: @gk01/re-dimitrisp-re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-servers-101-setting-up-a-web-server-part-3-ssl-20170815t185354908z
I see you had success, so I'll just leave these replies in case anyone with the same problems as you enters my post! If your ISP blocks port 80, you won't be able to host a webserver. You may be able to host a secure webserver (https) if they don't block port 443. You have to create a CName record instead of an A record for your `www.domainnamehere.com`, that points to `falez.ddns.net`. The problem is that you won't be able to use non-www domain (`domainnamehere.com` won't work). If you don't the next time you change IP, your site won't be available. Also, some providers may take up to 48 hours to update DNS records If you connect to a VPN, you may encounter problems. Connect to a different network altogether (saw you did that), and clear your dns cache! You won't be able to setup a DNS server on your network, as most, if not all, ISPs block incoming connections to port 53 that is being used for DNS lookups. It's in my plans to write a tutorial to setup your own DNS server, I'm just looking for a nice interface to include for not so tech-savvy people.
| author | dimitrisp |
|---|---|
| permlink | re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-servers-101-setting-up-a-web-server-part-3-ssl-20170815t203831138z |
| category | tutorial |
| json_metadata | {"tags":["tutorial"],"app":"steemit/0.1"} |
| created | 2017-08-15 20:38:30 |
| last_update | 2017-08-15 20:38:30 |
| depth | 6 |
| children | 8 |
| last_payout | 2017-08-22 20:38:30 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 1,074 |
| author_reputation | 75,800,974,934,104 |
| root_title | "Servers 101: Setting up a Web Server part 3 - SSL" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 11,915,738 |
| net_rshares | 619,520,000 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| gk01 | 0 | 619,520,000 | 100% |
Doesn't the CName point or resolve to the A Record? The A Records on Godaddy can only be actual IP addresses. You cannot use domains like falez.ddns.net as the A Record and therefore I'm not sure how I would point CNames to that domain? The last question I have is: If one's ISP blocks ports 80, 443, and or even 53, can't one simply use different ports to host a server or DNS server?
| author | gk01 |
|---|---|
| permlink | re-dimitrisp-re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-servers-101-setting-up-a-web-server-part-3-ssl-20170815t232516211z |
| category | tutorial |
| json_metadata | {"tags":["tutorial"],"app":"steemit/0.1"} |
| created | 2017-08-15 23:25:24 |
| last_update | 2017-08-15 23:25:24 |
| depth | 7 |
| children | 7 |
| last_payout | 2017-08-22 23:25:24 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 386 |
| author_reputation | 0 |
| root_title | "Servers 101: Setting up a Web Server part 3 - SSL" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 11,926,472 |
| net_rshares | 0 |
The CName is a totally different record to the A record. In a very simplified explanation, when you create a CName for `asd.domain.com` and point it to `asd.domain2.com` which in turn is an A record for `127.0.0.1`, you are basically telling the `asd.domain.com` to resolve to `127.0.0.1`. If at any point you change the A record of `asd.domain2.com` to `192.168.0.1`, then `asd.domain.com` will also resolve to this IP. So in your case, with a dynamic IP, this is the way to use your domain with your home connection. To my knowledge, services like DNS, can't be used on different ports. However, Web servers, FTP servers, SSH, and various other protocols, can be used at any port you want.
| author | dimitrisp |
|---|---|
| permlink | re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-servers-101-setting-up-a-web-server-part-3-ssl-20170816t061249008z |
| category | tutorial |
| json_metadata | {"tags":["tutorial"],"app":"steemit/0.1"} |
| created | 2017-08-16 06:12:51 |
| last_update | 2017-08-16 06:12:51 |
| depth | 8 |
| children | 6 |
| last_payout | 2017-08-23 06:12:51 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 696 |
| author_reputation | 75,800,974,934,104 |
| root_title | "Servers 101: Setting up a Web Server part 3 - SSL" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 11,953,042 |
| net_rshares | 0 |
Yes, I understand it's different from the A record. It stands for Canonical name, right? Your example is confusing. I guess what I could do is get rid of the A Record altogether, and then just use a CName (to point to the dynamic DNS domain that I obtained via noip.com which will always be mapped to my IP address). Is that possible?? If I got rid of the A Record, would that conflict with my SSL certificate (since the SSL certificate is probably mapped to my IP)?? Likewise, I was told that one reason why I might not be able to access my server online from my own network might have something to do with NAT. What do you know about this? P.S. You should make a tutorial on setting up file structures so that databases are accessible to websites that will be hosted. This is what I'm going to have to figure out how to do right now. I chose to install MySQL instead of MariaDB, so hopefully everything still works fine with the server as is. I don't see why it wouldn't.
| author | gk01 |
|---|---|
| permlink | re-dimitrisp-re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-re-gk01-re-dimitrisp-servers-101-setting-up-a-web-server-part-3-ssl-20170818t022841024z |
| category | tutorial |
| json_metadata | {"tags":["tutorial"],"app":"steemit/0.1"} |
| created | 2017-08-18 02:28:45 |
| last_update | 2017-08-19 01:13:48 |
| depth | 9 |
| children | 5 |
| last_payout | 2017-08-25 02:28:45 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 978 |
| author_reputation | 0 |
| root_title | "Servers 101: Setting up a Web Server part 3 - SSL" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 12,137,718 |
| net_rshares | 0 |
hiveblocks