Cloudflare - Revision history

M at 19:15, 25 November 2023

2023-11-25T19:15:03Z

@@ Line 10: / Line 10: @@
 Check the log for status.  A useful ddclient command that will vet its access to all network interfaces:
   ddclient -query
 == Email Forwarding ==
@@ Line 45: / Line 40: @@
      rule_name: shitcutter_redirect
 It's all a bit much, overengineered, but maybe someday will be useful.

M: /* Redirect one domain to another */

2023-11-25T19:03:31Z

Redirect one domain to another

← Older revision		Revision as of 19:03, 25 November 2023
Line 43:		Line 43:
	target https://shitcutter.com		target https://shitcutter.com
	status: 301		status: 301
			rule_name: shitcutter_redirect
			It's all a bit much, overengineered, but maybe someday will be useful.

M: /* Redirect one domain to another */

2023-11-25T19:00:50Z

Redirect one domain to another

← Older revision		Revision as of 19:00, 25 November 2023
Line 30:		Line 30:

	* Set up DNS records as usual (the domain has to resolve)		* Set up DNS records as usual (the domain has to resolve)
	* Use Bulk Redirects; Stupidly (or not?) you have to create a bulk redirect global list, then rules under it...		* Use Bulk Redirects
	** Create bulk redirect list		Stupidly (or not?) you have to create a bulk redirect global list, then rules under it... read on...

			* Create bulk redirect list
	domain > Rules > Redirect Rules > Bulk Redirects > Create build redirect list		domain > Rules > Redirect Rules > Bulk Redirects > Create build redirect list
	eg:		eg:
	name shitcutter_redirect		name shitcutter_redirect
	** Mange Bulk Redirect Rules		* Mange Bulk Redirect Rules
	domain > Rules > Redirect Rules > Bulk Redirects > Mange Bulk Redirect Rules		domain > Rules > Redirect Rules > Bulk Redirects > Mange Bulk Redirect Rules
	eg:		eg:

M: /* Redirect one domain to another */

2023-11-25T19:00:03Z

Redirect one domain to another

← Older revision		Revision as of 19:00, 25 November 2023
Line 30:		Line 30:

	* Set up DNS records as usual (the domain has to resolve)		* Set up DNS records as usual (the domain has to resolve)
	* Use Bulk Redirects		* Use Bulk Redirects; Stupidly (or not?) you have to create a bulk redirect global list, then rules under it...
	Stupidly (or not?) you have to create a bulk redirect global list, then rules under it.
	** Create bulk redirect list		** Create bulk redirect list
	domain > Rules > Redirect Rules > Bulk Redirects > Create build redirect list		domain > Rules > Redirect Rules > Bulk Redirects > Create build redirect list

M: /* Redirect one domain to another */

2023-11-25T18:59:44Z

Redirect one domain to another

← Older revision		Revision as of 18:59, 25 November 2023
Line 31:		Line 31:
	* Set up DNS records as usual (the domain has to resolve)		* Set up DNS records as usual (the domain has to resolve)
	* Use Bulk Redirects		* Use Bulk Redirects
	domain > Rules > Redirect Rules > Bulk Redirects > ~~Add...~~		Stupidly (or not?) you have to create a bulk redirect global list, then rules under it.
			** Create bulk redirect list
			domain > Rules > Redirect Rules > Bulk Redirects > Create build redirect list
			eg:
			name shitcutter_redirect
			** Mange Bulk Redirect Rules
			domain > Rules > Redirect Rules > Bulk Redirects > Mange Bulk Redirect Rules
	eg:		eg:
	source willcodeforcoffee.org/		source willcodeforcoffee.org/
	target https://shitcutter.com		target https://shitcutter.com
	status: 301		status: 301

M at 18:54, 25 November 2023

2023-11-25T18:54:15Z

← Older revision		Revision as of 18:54, 25 November 2023
Line 26:		Line 26:
	abettersoftware.com		abettersoftware.com
	abettertrader.com		abettertrader.com

			== Redirect one domain to another ==

			* Set up DNS records as usual (the domain has to resolve)
			* Use Bulk Redirects
			domain > Rules > Redirect Rules > Bulk Redirects > Add...
			eg:
			source willcodeforcoffee.org/
			target https://shitcutter.com
			status: 301

M: /* IP Change */

2023-11-25T18:47:16Z

IP Change

← Older revision		Revision as of 18:47, 25 November 2023
Line 5:		Line 5:
	ddclient is used to detect IP changes every 5 minutes. When it sees one, it calls the Cloudflare API to update the IP. WOW! ddclient runs as a service on bitpost, see the config file here:		ddclient is used to detect IP changes every 5 minutes. When it sees one, it calls the Cloudflare API to update the IP. WOW! ddclient runs as a service on bitpost, see the config file here:
	/etc/ddclient.conf		/etc/ddclient.conf
	~~Keep it synced with cloudflare domains, letsencrypt, haproxy, site code.~~

			Verbose logging is turned on, and logged to syslog, there. It is configured to check every 5 minutes. It includes all domains. Keep it synced with cloudflare domains, letsencrypt, haproxy, site code.

			Check the log for status. A useful ddclient command that will vet its access to all network interfaces:
			ddclient -query

			=== TODO ===
	After updating IP, it seems i have to disable proxy to get it to resolve. After a while, set it back on. Need to learn more here...		After updating IP, it seems i have to disable proxy to get it to resolve. After a while, set it back on. Need to learn more here...

			I have never allowed ddclient to do its thing after reboot yet. There will likely be work to get it to cooperate with stronger_firewall haproxy etc. See physical notes.

	== Email Forwarding ==		== Email Forwarding ==

M: /* IP Change */

2023-11-25T18:03:07Z

IP Change

← Older revision		Revision as of 18:03, 25 November 2023
Line 2:		Line 2:

	== IP Change ==		== IP Change ==

			ddclient is used to detect IP changes every 5 minutes. When it sees one, it calls the Cloudflare API to update the IP. WOW! ddclient runs as a service on bitpost, see the config file here:
			/etc/ddclient.conf
			Keep it synced with cloudflare domains, letsencrypt, haproxy, site code.

	After updating IP, it seems i have to disable proxy to get it to resolve. After a while, set it back on. Need to learn more here...		After updating IP, it seems i have to disable proxy to get it to resolve. After a while, set it back on. Need to learn more here...

M: /* Email Forwarding */

2023-11-25T18:00:25Z

Email Forwarding

← Older revision		Revision as of 18:00, 25 November 2023
Line 6:		Line 6:

	== Email Forwarding ==		== Email Forwarding ==
	Go to Email, ~~click around on~~ the ~~forwarding page until~~ it ~~suggests~~ adding the basic forwarding DNS records. Add them.		Go to Email, start the "wizard", add an initial routing, and it will suggest adding the basic forwarding DNS records. Add them.

	Then you have access to route emails to the domain. Route them to gmail. Use a catch-all until it is a problem (it hasn't been yet).		Then you have access to route emails to the domain. Route them to gmail. Use a catch-all until it is a problem (it hasn't been yet).

M: Created page with "Cloudflare seems to do everything I need and more: domain registration, DNS, domain forwarding, email forwarding, etc... and that world-class cloudflare proxying! == IP Change == After updating IP, it seems i have to disable proxy to get it to resolve. After a while, set it back on. Need to learn more here... == Email Forwarding == Go to Email, click around on the forwarding page until it suggests adding the basic forwarding DNS records. Add them. Then you have ac..."

2023-11-10T16:37:37Z

Created page with "Cloudflare seems to do everything I need and more: domain registration, DNS, domain forwarding, email forwarding, etc... and that world-class cloudflare proxying! == IP Change == After updating IP, it seems i have to disable proxy to get it to resolve. After a while, set it back on. Need to learn more here... == Email Forwarding == Go to Email, click around on the forwarding page until it suggests adding the basic forwarding DNS records. Add them. Then you have ac..."

New page

Cloudflare seems to do everything I need and more: domain registration, DNS, domain forwarding, email forwarding, etc... and that world-class cloudflare proxying!

== IP Change ==

After updating IP, it seems i have to disable proxy to get it to resolve. After a while, set it back on. Need to learn more here...

== Email Forwarding ==
Go to Email, click around on the forwarding page until it suggests adding the basic forwarding DNS records. Add them.

Then you have access to route emails to the domain. Route them to gmail. Use a catch-all until it is a problem (it hasn't been yet).

Email forwarding has been set up for...
thedigitalmachine.com
bitpost.com
abettersoftware.com
abettertrader.com