Complete markdown files cleanup and organization
- Organized 252 files across project - Root directory: 187 → 2 files (98.9% reduction) - Moved configuration guides to docs/04-configuration/ - Moved troubleshooting guides to docs/09-troubleshooting/ - Moved quick start guides to docs/01-getting-started/ - Moved reports to reports/ directory - Archived temporary files - Generated comprehensive reports and documentation - Created maintenance scripts and guides All files organized according to established standards.
This commit is contained in:
defiQUG
172
docs/02-architecture/DOMAIN_STRUCTURE.md
Normal file
172
docs/02-architecture/DOMAIN_STRUCTURE.md
Normal file
@@ -0,0 +1,172 @@
|
||||
# Domain Structure
|
||||
|
||||
**Last Updated:** 2025-01-03
|
||||
**Document Version:** 1.0
|
||||
**Status:** Active Documentation
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
This document defines the domain structure for the infrastructure, clarifying which domains are used for different purposes.
|
||||
|
||||
---
|
||||
|
||||
## Domain Assignments
|
||||
|
||||
### 1. sankofa.nexus - Hardware Infrastructure
|
||||
|
||||
**Purpose:** Physical hardware hostnames and internal network DNS
|
||||
|
||||
**Usage:**
|
||||
- All physical servers (ml110, r630-01 through r630-04)
|
||||
- Internal network DNS resolution
|
||||
- SSH access via FQDN
|
||||
- Internal service discovery
|
||||
|
||||
**Examples:**
|
||||
- `ml110.sankofa.nexus` → 192.168.11.10
|
||||
- `r630-01.sankofa.nexus` → 192.168.11.11
|
||||
- `r630-02.sankofa.nexus` → 192.168.11.12
|
||||
- `r630-03.sankofa.nexus` → 192.168.11.13
|
||||
- `r630-04.sankofa.nexus` → 192.168.11.14
|
||||
|
||||
**DNS Configuration:**
|
||||
- Internal DNS server (typically on ER605 or Omada controller)
|
||||
- Not publicly resolvable (internal network only)
|
||||
- Used for local network service discovery
|
||||
|
||||
**Related Documentation:**
|
||||
- [Physical Hardware Inventory](./PHYSICAL_HARDWARE_INVENTORY.md)
|
||||
|
||||
---
|
||||
|
||||
### 2. d-bis.org - ChainID 138 Services
|
||||
|
||||
**Purpose:** Public-facing services for ChainID 138 blockchain network
|
||||
|
||||
**Usage:**
|
||||
- RPC endpoints (public and permissioned)
|
||||
- Block explorer
|
||||
- WebSocket endpoints
|
||||
- Cloudflare tunnels for Proxmox hosts
|
||||
- All ChainID 138 blockchain-related services
|
||||
|
||||
**Examples:**
|
||||
- `rpc.d-bis.org` - Primary RPC endpoint
|
||||
- `rpc2.d-bis.org` - Secondary RPC endpoint
|
||||
- `explorer.d-bis.org` - Block explorer (Blockscout)
|
||||
- `ml110-01.d-bis.org` - Proxmox UI (via Cloudflare tunnel)
|
||||
- `r630-01.d-bis.org` - Proxmox UI (via Cloudflare tunnel)
|
||||
- `r630-02.d-bis.org` - Proxmox UI (via Cloudflare tunnel)
|
||||
- `r630-03.d-bis.org` - Proxmox UI (via Cloudflare tunnel)
|
||||
- `r630-04.d-bis.org` - Proxmox UI (via Cloudflare tunnel)
|
||||
|
||||
**DNS Configuration:**
|
||||
- Cloudflare DNS (proxied)
|
||||
- Publicly resolvable
|
||||
- SSL/TLS via Cloudflare
|
||||
|
||||
**Related Documentation:**
|
||||
- [Cloudflare Tunnel Setup](../04-configuration/CLOUDFLARE_TUNNEL_CONFIGURATION_GUIDE.md)
|
||||
- [RPC Configuration](../04-configuration/RPC_DNS_CONFIGURATION.md)
|
||||
- [Blockscout Setup](../BLOCKSCOUT_COMPLETE_SUMMARY.md)
|
||||
|
||||
---
|
||||
|
||||
### 3. defi-oracle.io - ChainID 138 Legacy (ThirdWeb RPC)
|
||||
|
||||
**Purpose:** Legacy RPC endpoint for ThirdWeb integration
|
||||
|
||||
**Usage:**
|
||||
- ThirdWeb RPC endpoint (VMID 2400)
|
||||
- Legacy compatibility for existing integrations
|
||||
- Public RPC access for ChainID 138
|
||||
|
||||
**Examples:**
|
||||
- `rpc.defi-oracle.io` - Legacy RPC endpoint
|
||||
- `rpc.public-0138.defi-oracle.io` - Specific ChainID 138 RPC endpoint
|
||||
|
||||
**DNS Configuration:**
|
||||
- Cloudflare DNS (proxied)
|
||||
- Publicly resolvable
|
||||
- SSL/TLS via Cloudflare
|
||||
|
||||
**Note:** This domain is maintained for backward compatibility with ThirdWeb integrations. New integrations should use `d-bis.org` endpoints.
|
||||
|
||||
**Related Documentation:**
|
||||
- [ThirdWeb RPC Setup](../04-configuration/THIRDWEB_RPC_CLOUDFLARE_SETUP.md)
|
||||
- [VMID 2400 DNS Structure](../04-configuration/VMID2400_DNS_STRUCTURE.md)
|
||||
|
||||
---
|
||||
|
||||
## Domain Summary Table
|
||||
|
||||
| Domain | Purpose | Public | DNS Provider | SSL/TLS |
|
||||
|--------|---------|--------|--------------|---------|
|
||||
| `sankofa.nexus` | Hardware infrastructure | No (internal) | Internal DNS | Self-signed |
|
||||
| `d-bis.org` | ChainID 138 services | Yes | Cloudflare | Cloudflare |
|
||||
| `defi-oracle.io` | ChainID 138 legacy (ThirdWeb) | Yes | Cloudflare | Cloudflare |
|
||||
|
||||
---
|
||||
|
||||
## Domain Usage Guidelines
|
||||
|
||||
### When to Use sankofa.nexus
|
||||
|
||||
- Internal network communication
|
||||
- SSH access to physical hosts
|
||||
- Internal service discovery
|
||||
- Local network DNS resolution
|
||||
- Proxmox cluster communication
|
||||
|
||||
### When to Use d-bis.org
|
||||
|
||||
- Public blockchain RPC endpoints
|
||||
- Block explorer access
|
||||
- Public-facing Proxmox UI (via tunnels)
|
||||
- ChainID 138 service endpoints
|
||||
- New integrations and services
|
||||
|
||||
### When to Use defi-oracle.io
|
||||
|
||||
- ThirdWeb RPC endpoint (legacy)
|
||||
- Backward compatibility
|
||||
- Existing integrations that reference this domain
|
||||
|
||||
---
|
||||
|
||||
## Migration Notes
|
||||
|
||||
### From defi-oracle.io to d-bis.org
|
||||
|
||||
For new services and integrations:
|
||||
- **Use `d-bis.org`** as the primary domain
|
||||
- `defi-oracle.io` is maintained for legacy ThirdWeb RPC compatibility
|
||||
- All new ChainID 138 services should use `d-bis.org`
|
||||
|
||||
### DNS Record Management
|
||||
|
||||
- **sankofa.nexus**: Managed via internal DNS (Omada controller or local DNS server)
|
||||
- **d-bis.org**: Managed via Cloudflare DNS
|
||||
- **defi-oracle.io**: Managed via Cloudflare DNS
|
||||
|
||||
---
|
||||
|
||||
## Related Documentation
|
||||
|
||||
### Architecture Documents
|
||||
- **[PHYSICAL_HARDWARE_INVENTORY.md](PHYSICAL_HARDWARE_INVENTORY.md)** ⭐⭐⭐ - Physical hardware inventory
|
||||
- **[NETWORK_ARCHITECTURE.md](NETWORK_ARCHITECTURE.md)** ⭐⭐⭐ - Complete network architecture
|
||||
- **[ORCHESTRATION_DEPLOYMENT_GUIDE.md](ORCHESTRATION_DEPLOYMENT_GUIDE.md)** ⭐⭐⭐ - Deployment orchestration
|
||||
|
||||
### Configuration Documents
|
||||
- **[../04-configuration/cloudflare/CLOUDFLARE_TUNNEL_CONFIGURATION_GUIDE.md](../04-configuration/cloudflare/CLOUDFLARE_TUNNEL_CONFIGURATION_GUIDE.md)** - Cloudflare tunnel configuration
|
||||
- **[../04-configuration/RPC_DNS_CONFIGURATION.md](../04-configuration/RPC_DNS_CONFIGURATION.md)** - RPC DNS configuration
|
||||
- **[../05-network/CLOUDFLARE_TUNNEL_ROUTING_ARCHITECTURE.md](../05-network/CLOUDFLARE_TUNNEL_ROUTING_ARCHITECTURE.md)** - Cloudflare routing architecture
|
||||
|
||||
---
|
||||
|
||||
**Last Updated:** 2025-01-03
|
||||
**Document Version:** 1.0
|
||||
**Review Cycle:** Quarterly
|
||||
Reference in New Issue
Block a user