How to deploy the own computer as a web server

Now, does a Web server need a static IP address to register to the DNS server and point the location?

No, the web server does not need a static IP. There are essentially three basic parts to hosting a website:

• The registrar (which updates the information for your site name -- ex. www.mysite.com)
• The Domain Name System (DNS) Server (which helps translate your site name to an actual IP used by your web server)
• Your web server

For example, www.mysite.com may hypothetically need to be associated with the IP 50.60.70.80, the address assigned to your computer via your ISP. DNS is what does does this.

The DNS server address itself needs to be (relatively) static so it can be found, but as long as the DNS server has a record of the appropriate IP address of your computer, it can forward data to that server. You can think of it like delivering a letter -- the Post Office (DNS server) has to stay in one place to receive mail but it can send mail wherever it likes (no matter how much you move).

How would you configure the DNS to point to a dynamic IP address?

You need to have a system where the DNS records are updated to match the current IP address of your web server. This can be done manually or automatically, depending on circumstances and preference.

Manually

If your comfortable with DNS records and don't have an IP that changes often...

• You can run a DNS server (such as BIND) yourself. While not generally difficult, you should be aware that there are potential complexity and security concerns with running your own DNS.

• You can manually update a third party DNS provider such as xname.org freedns.42.pl. These services offer you a form to create DNS records that are loaded to DNS servers which are hosted for you. However, this process isn't automated. You have to manually change the IP of your web server every time your ISP updates it.

Both of the above can cause issues with availability if your IP changes and so may not always be a good solution -- but they are doable even with a "dynamic" IP, assuming your ISP doesn't provide a new IP every time you connect.

Automatically

Since there is a market for less-than-technical people wanting domain names and DNS services, more and more automated services are being offered. These services often avoid most the of the hassles of DNS at the cost of some potential control of your DNS records.

Usually, a small program is downloaded to the web server which automatically keeps track of the web server's current IP as assigned by the ISP. This program, in turn, relays this information to a set of DNS servers, which are then automatically updated with the appropriate DNS records each time an IP address change is detected. Extending the first example given, it would be like hiring a butler to call the Post Office for you every time you moved so your mail could be forwarded appropriately.

Currently, there are generally two types of these services -- ones offered by DNS-only outfits such as No-IP and afraid.org and ones offered by domain registrars such as NameCheap.

• With DNS-only dynamic IP services, you are usually allowed to choose a URL/subdomain that will point to your computer (e.g. mysite.dyndns.com). People can then use this domain to directly access your web server.

If you want to use a registered domain such as www.mysite.com, you either have to forward that domain to your dynamic subdomain (e.g mysite.dyndns.com) or go through special procedures to allow the dynamic DNS company to directly associate www.mysite.com with their (automatically updated) DNS servers.

• If you are using a registrar that provides these services (again, such as NameCheap), this is not necessary. By default, when your register a domain name, the DNS servers associated with that domain name will be the registrar's. From there, all you need to do is download the dynamic DNS update program and everything should be automatically taken care of (e.g. www.mysite.com will be associated with your dynamic web server with no extra steps involved).

It's likely worth mentioning that NameCheap also has a FreeDNS service for existing domains. In short, what this means is that if your domain name is registered with a registrar that doesn't provide dynamic DNS, you may be able to switch your existing domain's DNS to NameCheap (without actually being their customer) and take advantage of their dynamic DNS services.

July 2020: Here is a list of alternatives to Xname.org. Most of them are not updated manually, but they all should provide free dynamic DNS.

According to the screenshots you are showing, you have port forwarding oddly set on your WAN connection as follows:

• External Port Start/End: 80/80
• Protocol: TCP
• Internal Port Start/End: 80/80
• Server IP Address: 192.168.1.11
• Schedule Rule: Always
• Remote IP: 192.168.1.11

The way you have that setup basically tells the router to just route all traffic from 192.168.1.11 on port 80 to 192.168.1.11 on port 80 which makes no sense. The “Remote IP:” should be set to your external IP address of 117.218.XXX.XXX like this:

• Remote IP: 117.218.XXX.XXX

With that in place that tells the router to route all traffic from 117.218.XXX.XXX on port 80 to 192.168.1.11 on port 80.

That said, if the router itself uses port 80 for the D-Link management page, then you need to see if you can change the port that management page uses. Otherwise all you are doing with that ruleset is exposing your D-Link management page to anyone/anything that can reach that 117.218.XXX.XXX. As to how to do that? Each router has different ways to handle that and some routers just don’t provide end users with that option since ISP’s generally don’t want end-users to easily run web servers off of their ISP-provided Internet connection.

If you cannot change the D-Link management page port to be something other than port 80 the next best thing is to just change your web server’s port to be something else, like 8000 or 8080. Of course you now need to adjust your port forwarding rules to match the new port, but it might be the best/simplest solution to this issue.