CGHMN DNS Information - Revision history

Snep: Update dnsmasq update script

2026-03-22T00:15:31Z

Update dnsmasq update script

← Older revision		Revision as of 17:15, 21 March 2026
Line 92:		Line 92:
	== dnsmasq Synchronization Script ==		== dnsmasq Synchronization Script ==
	Since the CGHMN offers custom TLDs, keeping up with which domains are part of the CGHNM can become quite difficult. For this, @Snep built a small script (which is rather hacky, but works) that can be added on Linux systems which have dnsmasq running as their DNS resolver. It only needs <code>wget</code>, <code>grep</code> and <code>md5sum</code> (the BusyBox variants shipped with OpenWRT are fine). Download the following script to your router, for example into your root directory:		Since the CGHMN offers custom TLDs, keeping up with which domains are part of the CGHNM can become quite difficult. For this, @Snep built a small script (which is rather hacky, but works) that can be added on Linux systems which have dnsmasq running as their DNS resolver. It only needs <code>wget</code>, <code>grep</code> and <code>md5sum</code> (the BusyBox variants shipped with OpenWRT are fine). Download the following script to your router, for example into your root directory:
	wget -O /root/update-dns-forwards.sh "https://raw.githubusercontent.com/CGHMN/openwrt-~~connect-script~~/refs/heads/main/~~openwrt~~/update-dns-forwards.sh"		wget -O /root/update-dns-forwards.sh "https://raw.githubusercontent.com/CGHMN/openwrt-scripts/refs/heads/main/dns/update-dns-forwards.sh"
	Next, run it manually once to make sure the CGHMN DNS configuration file exists and the script runs through without issue:		Next, run it manually once to make sure the CGHMN DNS configuration file exists and the script runs through without issue:
	/bin/sh /root/update-dns-forwards.sh		/bin/sh /root/update-dns-forwards.sh

Snep: Updated DNS updater script

2026-03-01T03:05:24Z

Updated DNS updater script

@@ Line 91: / Line 91: @@
 == dnsmasq Synchronization Script ==
-Since the CGHMN offers custom TLDs, keeping up with which domains are part of the CGHNM can become quite difficult. For this, @Snep built a small script (which is rather hacky, but works) that can be added on Linux systems which have dnsmasq running as their DNS resolver. It only needs <code>wget</code> (the BusyBox variant is fine) and <code>md5sum</code>. Insert the following text to <code>/root/update-cghmn-domains.sh</code>:
+Since the CGHMN offers custom TLDs, keeping up with which domains are part of the CGHNM can become quite difficult. For this, @Snep built a small script (which is rather hacky, but works) that can be added on Linux systems which have dnsmasq running as their DNS resolver. It only needs <code>wget</code>, <code>grep</code> and <code>md5sum</code> (the BusyBox variants shipped with OpenWRT are fine). Download the following script to your router, for example into your root directory:
- #!/bin/sh
+ wget -O /root/update-dns-forwards.sh "https://raw.githubusercontent.com/CGHMN/openwrt-connect-script/refs/heads/main/openwrt/update-dns-forwards.sh"
 Next, run it manually once to make sure the CGHMN DNS configuration file exists and the script runs through without issue:
-  /bin/sh /root/update-cghmn-domains.sh
+  /bin/sh /root/update-dns-forwards.sh
 Then, you can include the newly created configuration file in your dnsmasq instance. For OpenWRT devices, nagivate to Network -> DHCP and DNS -> Forwards and add <code>/etc/cghmn-domains.dnsmasq.conf</code> in the "Additional servers file" field, then hit "Save & Apply". On other systems, append the following line to your <code>dnsmasq.conf</code> file:
   conf-file=/etc/cghmn-domains.dnsmasq.conf
 Finally, to have the list get updated automatically every 15 minutes, add the following to your crontab (e.g. <code>crontab -e</code> as root):
-  */15 * * * * /bin/sh /root/update-cghmn-domains.sh
+  */15 * * * * /bin/sh /root/update-dns-forwards.sh
 [[Category:Compu-Global-Hyper-Mega-Net]]

Snep: Add dnsmasq sync script

2026-02-15T01:58:12Z

Add dnsmasq sync script

@@ Line 89: / Line 89: @@
 === DNS manipulation with multiple RR types ===
 If a record is being looked up, and this record was once an A record, but still exists and is now a CNAME record, you will have an issue where the lookup will work with tools, but fail with actual lookups.  This is because the CNAME record being returned from the real DNS server will take precedent over the fake A record.  To resolve this issue, you have to fake both the CNAME and the A record.
 [[Category:Compu-Global-Hyper-Mega-Net]]

Snep at 00:41, 25 December 2025

2025-12-25T00:41:15Z

← Older revision		Revision as of 17:41, 24 December 2025
Line 7:		Line 7:

	==== Pointing to the right DNS server ====		==== Pointing to the right DNS server ====
	CGHMN has several DNS servers in use for differing purposes. '''The correct default DNS server you should be pointing at while getting started is ~~172~~.23.0.1 from the core network, or 100.89.128.0 from the Wireguard tunnel'''. This is the router, which then forwards the requests to the actual DNS.		CGHMN has several DNS servers in use for differing purposes. '''The correct default DNS server you should be pointing at while getting started is 100.64.21.1 from the core network, or 100.89.128.0 from the Wireguard tunnel'''. This is the router, which then forwards the requests to the actual DNS.

	==== What the different DNS servers are (or, is this thing on?) ====		==== What the different DNS servers are (or, is this thing on?) ====
	CGHMN's DNS is configured such that there are three core servers that perform response modifications to allow the recreation of long defunct services, perform lookups, and act as the root name server for the network, which has two internal TLD (top level domain, like .com or .net) on it.		CGHMN's DNS is configured such that there are three core servers that perform response modifications to allow the recreation of long defunct services, perform lookups, and act as the root name server for the network, which has two internal TLD (top level domain, like .com or .net) on it.

	===== ~~172~~.23.4.~~101~~ - ns1.cghmn =====		===== 100.64.11.11 - ns1.cghmn =====
	This is the root name server for the .retro and .cghmn TLDs, as well as the ~~23.172.in-addr.arpa and 96.~~100.in-addr.arpa reverse lookup ~~zones~~. This server exists to delegate domains to members of CGHMN, and serve as the name server for the internal network. This server is useful to perform a <code>dig</code> or <code>nslookup</code> against if you want to see if a subdomain has been delegated, for example:		This is the root name server for the .retro and .cghmn TLDs, as well as the 100.in-addr.arpa reverse lookup zone. This server exists to delegate domains to members of CGHMN, and serve as the name server for the internal network. This server is useful to perform a <code>dig</code> or <code>nslookup</code> against if you want to see if a subdomain has been delegated, for example:

	<code>dig ns example.retro. @~~172~~.23.4.~~101~~</code>		<code>dig ns example.retro. @100.64.11.11</code>

	or		or
	nslookup		nslookup

	> server ~~172~~.23.4.~~101~~		> server 100.64.11.11

	> set type=ns		> set type=ns
Line 27:		Line 27:
	This server does not perform lookups. It is currently running BIND.		This server does not perform lookups. It is currently running BIND.

	===== 172.23.4.105 =====		===== <s>172.23.4.105</s> =====
	This is the recursive lookup server for the network. It is configured to recursively look up all requests for CGHMN domains, starting with ns1.cghmn, and then moving up based on delegations to member servers. Regular lookups still take place against real TLDs, if something needs to be pulled off the internet. This server is currently running BIND. This server is useful to use <code>dig</code> or <code>nslookup</code> against if you wish to see if your domain is resolving on the network after it has been delegated to you.		<s>This is the recursive lookup server for the network. It is configured to recursively look up all requests for CGHMN domains, starting with ns1.cghmn, and then moving up based on delegations to member servers. Regular lookups still take place against real TLDs, if something needs to be pulled off the internet. This server is currently running BIND. This server is useful to use <code>dig</code> or <code>nslookup</code> against if you wish to see if your domain is resolving on the network after it has been delegated to you.</s>

	<code>dig a test.example.retro. @172.23.4.105</code>		<code><s>dig a test.example.retro. @172.23.4.105</s></code>

	or		<s>or</s>
	nslookup		<s>nslookup

	> server 172.23.4.105		> server 172.23.4.105
Line 39:		Line 39:
	> set type=a		> set type=a

	> test.example.retro.		> test.example.retro.</s>

	===== 172.23.4.104 - legacydns.cghmhn =====		===== <s>172.23.4.104 - legacydns.cghmhn</s> =====
	This is a dnsmasq server that is currently being used to perform modifications to DNS answers, by pulling from a list of servers that need to be faked in order to make old software, such as AIM, work correctly. This server overrides the DNS answer with these responses, so all relevant DNS records need to be added. The rationale for this is that instead of a user modifying their hosts file (which can be dozens of different DNS addresses long) we can simply return addresses that correspond within the network. Please ask if there is a service you would like added to the network that requires this kind of override. Otherwise, it just forwards the questions to the recursive lookup server 172.23.4.105. This server is useful to test against if you are having trouble connecting to a legacy service that utilizes hard coded DNS.		<s>This is a dnsmasq server that is currently being used to perform modifications to DNS answers, by pulling from a list of servers that need to be faked in order to make old software, such as AIM, work correctly. This server overrides the DNS answer with these responses, so all relevant DNS records need to be added. The rationale for this is that instead of a user modifying their hosts file (which can be dozens of different DNS addresses long) we can simply return addresses that correspond within the network. Please ask if there is a service you would like added to the network that requires this kind of override. Otherwise, it just forwards the questions to the recursive lookup server 172.23.4.105. This server is useful to test against if you are having trouble connecting to a legacy service that utilizes hard coded DNS.</s>

	<code>dig cname login.oscar.aol.com.</code>		<code><s>dig cname login.oscar.aol.com.</s></code>

	or		<s>or</s>
	nslookup		<s>nslookup

	> server 172.23.4.104		> server 172.23.4.104
Line 53:		Line 53:
	> set type=cname		> set type=cname

	> login.oscar.aol.com.		> login.oscar.aol.com.</s>

	===== ~~172~~.23.0.1 =====		===== 100.64.12.1 or 100.64.11.1 =====
	This is the core router for the network, which also serves as a DNS forwarding. It ~~is currently forwarding all traffic~~ to ~~legacydns~~.cghmn, and ~~performs no additional lookups~~ or ~~translation~~. ~~This server is useful to test against for any purpose~~.		This is the core router for the network, which also serves as a DNS forwarding. It forwards requests to .retro and .cghmn to ns1.cghmn, whilst resolving some legacy DNS overrides and custom DNS domains according to its local configuration. To get a list of domains for which this DNS resolver has overrides or local forwards configured, you can cURL/wget this URL: http://100.64.12.1:8080/dns-forward-domains.txt or if you're running dnsmasq as your resolver at home, directly include the configuration file available at http://100.64.12.1:8080/dns-forward-domains.dnsmasq.conf.

	== Hosting Your Own DNS Name Server ==		== Hosting Your Own DNS Name Server ==

Snep: Added info about default DNS being 100.89.128.0 in the WG tunnel

2025-05-16T06:49:26Z

Added info about default DNS being 100.89.128.0 in the WG tunnel

← Older revision		Revision as of 23:49, 15 May 2025
Line 7:		Line 7:

	==== Pointing to the right DNS server ====		==== Pointing to the right DNS server ====
	CGHMN has several DNS servers in use for differing purposes. '''The correct default DNS server you should be pointing at while getting started is 172.23.0.1'''. This is the router, which then forwards the requests to the actual DNS.		CGHMN has several DNS servers in use for differing purposes. '''The correct default DNS server you should be pointing at while getting started is 172.23.0.1 from the core network, or 100.89.128.0 from the Wireguard tunnel'''. This is the router, which then forwards the requests to the actual DNS.

	==== What the different DNS servers are (or, is this thing on?) ====		==== What the different DNS servers are (or, is this thing on?) ====

Talija: Added hosting your own and weird quirks

2025-05-16T02:31:05Z

Added hosting your own and weird quirks

@@ Line 57: / Line 57: @@
 ===== 172.23.0.1 =====
 This is the core router for the network, which also serves as a DNS forwarding.  It is currently forwarding all traffic to legacydns.cghmn, and performs no additional lookups or translation.  This server is useful to test against for any purpose.
 [[Category:Compu-Global-Hyper-Mega-Net]]

CursedSilicon: Minor formatting tweak, added info about legacy DNS

2025-05-16T00:27:41Z

Minor formatting tweak, added info about legacy DNS

← Older revision		Revision as of 17:27, 15 May 2025
Line 7:		Line 7:

	==== Pointing to the right DNS server ====		==== Pointing to the right DNS server ====
	CGHMN has several DNS servers in use for differing purposes. The correct default DNS server you should be pointing at while getting started is 172.23.0.1. This is the router, which then forwards the requests to the actual DNS.		CGHMN has several DNS servers in use for differing purposes. '''The correct default DNS server you should be pointing at while getting started is 172.23.0.1'''. This is the router, which then forwards the requests to the actual DNS.

	==== What the different DNS servers are (or, is this thing on?) ====		==== What the different DNS servers are (or, is this thing on?) ====
Line 42:		Line 42:

	===== 172.23.4.104 - legacydns.cghmhn =====		===== 172.23.4.104 - legacydns.cghmhn =====
	This is a dnsmasq server that is currently being used to perform modifications to DNS answers, by pulling from a list of servers that need to be faked in order to make old software, such as AIM, work correctly. This server overrides the DNS answer with these responses, so all relevant DNS records need to be added. Please ask if there is a service you would like added to the network that requires this kind of override. Otherwise, it just forwards the questions to the recursive lookup server 172.23.4.105. This server is useful to test against if you are having trouble connecting to a legacy service that utilizes hard coded DNS.		This is a dnsmasq server that is currently being used to perform modifications to DNS answers, by pulling from a list of servers that need to be faked in order to make old software, such as AIM, work correctly. This server overrides the DNS answer with these responses, so all relevant DNS records need to be added. The rationale for this is that instead of a user modifying their hosts file (which can be dozens of different DNS addresses long) we can simply return addresses that correspond within the network. Please ask if there is a service you would like added to the network that requires this kind of override. Otherwise, it just forwards the questions to the recursive lookup server 172.23.4.105. This server is useful to test against if you are having trouble connecting to a legacy service that utilizes hard coded DNS.

	<code>dig cname login.oscar.aol.com.</code>		<code>dig cname login.oscar.aol.com.</code>

Talija: Initial post, creating to add a summary of the different DNS servers on the network.

2025-05-16T00:02:53Z

Initial post, creating to add a summary of the different DNS servers on the network.

New page

== About this page ==
This page exists to document information about the DNS of CGHMN, and some of the complexities that comes with a DNS infrastructure made of up varying platforms across decades of the protocol's evolution. See [[CGHMN-Demo-Network]] for detailed information about the underlying infrastructure

== DNS Configuration Guide ==

=== Getting Started ===

==== Pointing to the right DNS server ====
CGHMN has several DNS servers in use for differing purposes. The correct default DNS server you should be pointing at while getting started is 172.23.0.1. This is the router, which then forwards the requests to the actual DNS.

==== What the different DNS servers are (or, is this thing on?) ====
CGHMN's DNS is configured such that there are three core servers that perform response modifications to allow the recreation of long defunct services, perform lookups, and act as the root name server for the network, which has two internal TLD (top level domain, like .com or .net) on it.

===== 172.23.4.101 - ns1.cghmn =====
This is the root name server for the .retro and .cghmn TLDs, as well as the 23.172.in-addr.arpa and 96.100.in-addr.arpa reverse lookup zones. This server exists to delegate domains to members of CGHMN, and serve as the name server for the internal network. This server is useful to perform a <code>dig</code> or <code>nslookup</code> against if you want to see if a subdomain has been delegated, for example:

<code>dig ns example.retro. @172.23.4.101</code>

or
nslookup

> server 172.23.4.101

> set type=ns

> example.retro.
This server does not perform lookups. It is currently running BIND.

===== 172.23.4.105 =====
This is the recursive lookup server for the network. It is configured to recursively look up all requests for CGHMN domains, starting with ns1.cghmn, and then moving up based on delegations to member servers. Regular lookups still take place against real TLDs, if something needs to be pulled off the internet. This server is currently running BIND. This server is useful to use <code>dig</code> or <code>nslookup</code> against if you wish to see if your domain is resolving on the network after it has been delegated to you.

<code>dig a test.example.retro. @172.23.4.105</code>

or
nslookup

> server 172.23.4.105

> set type=a

> test.example.retro.

===== 172.23.4.104 - legacydns.cghmhn =====
This is a dnsmasq server that is currently being used to perform modifications to DNS answers, by pulling from a list of servers that need to be faked in order to make old software, such as AIM, work correctly. This server overrides the DNS answer with these responses, so all relevant DNS records need to be added. Please ask if there is a service you would like added to the network that requires this kind of override. Otherwise, it just forwards the questions to the recursive lookup server 172.23.4.105. This server is useful to test against if you are having trouble connecting to a legacy service that utilizes hard coded DNS.

<code>dig cname login.oscar.aol.com.</code>

or
nslookup

> server 172.23.4.104

> set type=cname

> login.oscar.aol.com.

===== 172.23.0.1 =====
This is the core router for the network, which also serves as a DNS forwarding. It is currently forwarding all traffic to legacydns.cghmn, and performs no additional lookups or translation. This server is useful to test against for any purpose.
[[Category:Compu-Global-Hyper-Mega-Net]]