DynDNS - Revision history

Admin at 18:10, 11 January 2019

2019-01-11T18:10:00Z

← Older revision		Revision as of 18:10, 11 January 2019
Line 1:		Line 1:
			Take note: https://twitter.com/wesmckinn/status/1080987957983617026

			"TIL Google Domains offers free Dynamic DNS. Won't be paying DynDNS in the future"

	= Client =		= Client =

Admin at 15:59, 28 May 2011

2011-05-28T15:59:17Z

← Older revision		Revision as of 15:59, 28 May 2011
Line 33:		Line 33:


	~~[[Category:Computers]]~~		{{Programs}}
	~~[[Category:~~Programs]]

Admin: /* Cloaking */

2011-03-15T23:59:33Z

Cloaking

← Older revision		Revision as of 23:59, 15 March 2011
Line 24:		Line 24:
	* For example, people would enter www.example.com, and be redirected to web.example.com:8080		* For example, people would enter www.example.com, and be redirected to web.example.com:8080

	(~~Still~~ not ~~sure exactly~~ what the ~~person who posted means by this~~...)		'''DOES NOT WORK''': This approach doesn't work, because entering www.example.com (which then WebHops to web.example.com:8080, which then WebHops to 127.0.0.1:8080) doesn't keep "www.example.com" in the browser address bar. It puts the IP address, "127.0.0.1:8080", in the browser bar. This approach also fails if www.example.com is a CNAME redirect to web.example.com (which, by the way, can't contain

			Another approach:
			* http://www.dyndnscommunity.com/questions/5861/custom-dns-cloaking-not-what-i-expected
			* First, the site web.example.com is a DNS A record (i.e. a "Hostname" option, with "Host with IP address" selected, forwarding to the IP address 127.0.0.1 - NO PORT!)
			* Next, the site that users visit is www.example.com, which is a WebHop to "http://web.example.com:8080" - which should, in theory, resolve into http://www.example.com:8080



	[[Category:Computers]]		[[Category:Computers]]
	[[Category:Programs]]		[[Category:Programs]]

Admin at 23:49, 15 March 2011

2011-03-15T23:49:28Z

← Older revision		Revision as of 23:49, 15 March 2011
Line 17:		Line 17:
	(or wherever else you might have put your startup item).		(or wherever else you might have put your startup item).

			= Cloaking =

			Webhop approach to cloaking, for non-standard port numbers
			* http://www.dyndnscommunity.com/questions/1167/forwarding-cloaking-refresh-question
			* To hide your server's IP address using a non-standard port, create 2 hostnames: one that people enter, and one that resolves your IP.
			* For example, people would enter www.example.com, and be redirected to web.example.com:8080

			(Still not sure exactly what the person who posted means by this...)


	[[Category:Computers]]		[[Category:Computers]]
	[[Category:Programs]]		[[Category:Programs]]

Admin at 23:23, 4 October 2010

2010-10-04T23:23:38Z

← Older revision		Revision as of 23:23, 4 October 2010
Line 16:		Line 16:

	(or wherever else you might have put your startup item).		(or wherever else you might have put your startup item).



			[[Category:Computers]]
			[[Category:Programs]]

Admin: Created page with "= Client = == Unix == Unix-based operating systems don't have a convenient GUI for automatically updating a dynamic IP address for a server with the DynDNS servers. However, i..."

2010-10-04T05:32:46Z

Created page with "= Client = == Unix == Unix-based operating systems don't have a convenient GUI for automatically updating a dynamic IP address for a server with the DynDNS servers. However, i..."

New page

= Client =

== Unix ==

Unix-based operating systems don't have a convenient GUI for automatically updating a dynamic IP address for a server with the DynDNS servers. However, it can still be done using ddclient, a perl script that allows for updating of the server's IP address. It has several nice features, one of which is the ability to run in the background in daemon mode.

The basic idea is this: create an executable script that will detect the IP address and send it to the DynDNS servers. Create a configuration file so that the executable knows what information to tell the DynDNS servers. And finally, create a startup item so that ddclient will run in the background.

Once you download the tarball, untar it and put one of the sample init files (sample-etc_rc.d_init.d_ddclient or similar) into <code>/etc/init.d</code> or <code>/etc/rd.d</code> or wherever startup items go for your *nix flavor. When you edit this startup script, you will be able to point the script to the ddclient executable script (wherever you decide to put it, [http://sourceforge.net/apps/trac/ddclient the ddclient web page] recommends <code>/usr/sbin</code>) and the configuration file (wherever you decide to put it, [http://sourceforge.net/apps/trac/ddclient the ddclient web page] recommends <code>/etc/ddclient/ddclient.conf</code>.

Next, copy the executable ddclient script to wherever you have decided to put it. Likewise, copy the example ddclient configuration file to ddclient.conf in whatever location you have decided to put it. When you're finished, test it out by starting the startup item by hand:

<pre>
/etc/init.d/ddclient start
</pre>

(or wherever else you might have put your startup item).