Configuration of a HTTP server on local computer using Dynamic DNS
Configuring a HTTP Server on your local computer using Dynamic DNS
Requirements: HTTP Server (XAMPP/LAMPP Chosen here)
Purpose: We demonstrated how to setup a local HTTP server using Apache (preinstalled using XAMPP).
If this web page was to be accessed globally from the internet, our IP address would have to be referenced (say http://202.124.23.33/ , however if our IP is dynamic, it is difficult to keep track of our web page’s address). Even using a registered domain name would not help ( http://www.somedomain.com/ ) as it would not be able to keep track of our dynamically changing IP, which is the usual case for most home internet users.
Solution: We use a facility of our test router called dynamic DNS.
Dynamic DNS is a method, protocol, or network service that provides the capability for a networked device, such as a router or computer system using the Internet Protocol Suite, to notify a domain name server to change, in real time (ad-hoc) the active DNS configuration of its configured hostnames, addresses or other information stored in DNS.
A popular application of dynamic DNS is to provide a residential user’s Internet gateway that has a variable, often changing, IP address with a well known hostname resolvable by network applications through standard DNS queries.
Function
Dynamic DNS providers provide a software client program that automates the discovery and registration of client’s public IP addresses. The client program is executed on a computer or device in the private network. It connects to the service provider’s systems and causes those systems to link the discovered public IP address of the home network with a hostname in the domain name system. Depending on the provider, the hostname is registered within a domain owned by the provider or the customer’s own domain name. These services can function by a number of mechanisms. Often they use an HTTP service request since even restrictive environments usually allow HTTP service. This group of services is commonly also referred to by the term Dynamic DNS, although it is not the standards-based DNS Update method. However, the latter might be involved in the providers systems.
Most home networking routers today have this feature already built into their firmware. One of the early routers to support Dynamic DNS was the UMAX UGate-3000 in 1999, which supported the TZO.COM dynamic DNS service.
An example of use is a home user who wishes to access a computer on a home network while travelling. The user may be supplied with a different IP address every time an Internet connection to the service provider is made, so there is no stable address to connect to. If a DDNS service is used to associate a fixed address to a device, then the user can, for example, establish a Virtual Private Network (VPN) to the network using that address. As a detailed example, the IP address can be 123.234.111.112 one day, 123.124.45.15 the next, but the DDNS address will always be, say, myhome.ddns.org. A remote control program such as VNC server can be left running on a machine in the network; the user can connect to the network by establishing a password-protected VPN to myhome.ddns.org, then connect to the machine using a VNC client program.
In Microsoft Windows networks, Dynamic DNS is an integral part of Active Directory, because domain controllers register their network service types in DNS so that other computers in the Domain (or Forest) can access them.
Increasing efforts to secure Internet communications today involve encryption of all dynamic updates via the public Internet, as these public dynamic DNS services have been abused increasingly to design security breaches. Standards-based methods within the DNSSEC protocol suite, such as TSIG, have been developed to secure DNS updates, but are not widely in use. Microsoft developed alternative technology (GSS-TSIG) based on Kerberos authentication.


Recent Comments