Changes for page REMC1 Member Shared I.T. Documentation Main Page
Last modified by Josh Hiner on 2026/08/19 16:33
From version 6.1
edited by Josh Hiner
on 2025/07/07 12:04
on 2025/07/07 12:04
Change comment:
There is no comment for this version
To version 4.1
edited by Josh Hiner
on 2022/12/28 10:27
on 2022/12/28 10:27
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -2,24 +2,6 @@ 2 2 3 3 REMC1 has created this Public facing page to share out potentially useful I.T. documentation with other REMC1 members. This page will slowly populated with any I.T. documentation thought to be helpful for others. 4 4 5 -= {{id name="REMC1-WAN-Connection-Information"/}}REMC1 WAN Connection Information = 6 - 7 -== {{id name="REMC1-WAN-DNS-Servers---Recommended-to-utilize-REMC1-internal-services"/}}REMC1 WAN DNS Servers - Recommended to utilize REMC1 internal services == 8 - 9 -=== {{id name="We-recommend-ALWAYS-using-the-REMC1-DNS-servers-listed-below-to:"/}}We recommend ALWAYS using the REMC1 DNS servers listed below to: === 10 - 11 -(% start="1" %) 12 -1. Properly resolve our internal addresses for our member services such as: [[support.remc1.net>>url:http://support.remc1.net||shape="rect"]], [[intermapper.remc1.net>>url:http://intermapper.remc1.net||shape="rect"]] (network monitoring), DNS that points to your Fortigate vdom interface for controlling your firewall rules, webfiltering/app control/IDS/IPS, REMC1 Apple Cache/MSUS system and other add-on services. 13 -1. To take advantage of our MDBR (malicious domain blocking and reporting) and automatic malicious dns filtering. 14 -1. Our DNS servers are in close proximity to you and thus very fast. 15 -1. Without using our DNS you may not be taking advantage of MISEN and MERIT direct peering fast paths: We utilize MISEN/MERIT dns as our forwarders to take advantage of their peering and on-net dns resolution for Amazon EC2 peering, Netflix peering etc.. Using our DNS ensures you follow the faster peering paths vs global generic paths that are off-net and most likely slower. 16 - 17 -==== {{id name="REMC1-Internal-DNS-Servers"/}}REMC1 Internal DNS Servers ==== 18 - 19 -* [[dns1.remc1.net>>url:http://dns1.remc1.net||shape="rect"]] - 10.22.1.1 20 -* [[dns2.remc1.net>>url:http://dns2.remc1.net||shape="rect"]] - 10.22.1.2 21 -* [[dns3.remcq.net>>url:http://dns3.remcq.net||shape="rect"]] - 10.22.1.3 22 - 23 23 = {{id name="Page-Links"/}}Page Links = 24 24 25 25 == {{id name="Networking"/}}Networking ==
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 -1217 6921371 +1217725205