DNS & Whitelisting
The Connec2 platform can be accessed from any network that meets the requirements below.
If permitted by your telecom provider, it can even be accessed via a mobile 4G or 5G connection.
For full functionality, your network administrator may need to adjust DNS records and whitelist several domains and ports.
DNS Records — connec2.app
All records below are proxied and secured via Cloudflare’s global edge network.
| Name | DNS Record Type | Value | Proxied by Cloudflare |
|---|---|---|---|
@ | CNAME | connec2.pages.dev | ✅ Yes |
cdn | CNAME | connec2-cdn.developer-013.workers.dev | ✅ Yes |
docs | CNAME | connec2-docs.pages.dev | ✅ Yes |
www | CNAME | connec2.pages.dev | ✅ Yes |
Whitelisting Cloudflare Network
To ensure connectivity with connec2.app, allow outbound and inbound HTTPS (TCP 443)
from Cloudflare’s official IP ranges. These are published and maintained at:
⚙️ Recommendation: Don’t manually enter individual IPs.
Instead, automate or periodically sync the list from Cloudflare to keep your firewall rules up to date.
Cloudflare Public DNS (optional)
| Purpose | IPv4 | IPv6 |
|---|---|---|
| Primary | 1.1.1.1 | 2606:4700:4700::1111 |
| Secondary | 1.0.0.1 | 2606:4700:4700::1001 |
These resolvers offer fast, secure, and privacy-focused DNS resolution for internal testing or fallback configurations.
DNS Records — connec2.nl
| Name | DNS Record Type | Value |
|---|---|---|
* | A | 85.10.159.32 |
@ | A | 85.10.159.32 |
eu-nl-ams-0 | A | 185.10.50.94 |
eu-nl-ams-1 | A | 84.247.14.175 |
www | CNAME | @ |
Whitelisting
Core Services
| FQDN | IP Address | Protocol | Port(s) | Description |
|---|---|---|---|---|
www.connec2.nl | 85.10.159.32 | TCP / HTTPS | 443 | Connec2 Website |
uplink.connec2.nl | 85.10.159.32 | TCP / HTTPS | 443 | Connec2 Uplink Installer |
login.connec2.nl | 85.10.159.32 | TCP / HTTPS | 443 | Connec2 Cluster Redirection |
packages.connec2.nl | 85.10.159.32 | TCP / HTTPS | 443 | Uplink Package Repository |
api.connec2.nl | 85.10.159.32 | TCP / HTTPS | 443 | Connec2 API Service |
content.connec2.nl | 85.10.159.32 | TCP / HTTPS | 443 | Web Content (e.g. scripts) |
Clusters
| Cluster | IP Address | Protocol | Port(s) | Description |
|---|---|---|---|---|
eu-nl-ams-0.connec2.nl | 185.10.50.94 | TCP / HTTPS | 443 | Management Console / Cloud API |
eu-nl-ams-0.connec2.nl | 185.10.50.94 | TCP / WS+AES | 9000–9099 | XR Services Data Channels (real-time) |
eu-nl-ams-1.connec2.nl | 84.247.14.175 | TCP / HTTPS | 443 | Management Console / Cloud API |
eu-nl-ams-1.connec2.nl | 84.247.14.175 | TCP / WS+AES | 9000–9099 | XR Services Data Channels (real-time) |
Note: Connec2 XR Services Data Channels must be directly connected to achieve optimal VR/AR performance (low latency).
Avatar Provider (Wolf3D / Ready Player Me)
| FQDN | IP Address | Protocol | Port(s) | Description |
|---|---|---|---|---|
models.readyplayer.me | – | TCP / HTTPS | 443 | Avatar Model Delivery |
avatars.readyplayer.me | – | TCP / HTTPS | 443 | Avatar Textures & Metadata |
connec2.readyplayer.me | – | TCP / HTTPS | 443 | Connec2 Avatar Editor |
Summary
For uninterrupted use of Connec2 Cloud, ensure:
- All listed domains are resolvable via DNS.
- Your firewall allows outbound HTTPS (443) and WebSocket AES (9000–9099) connections.
- Internal policies permit secure access to the listed Wolf3D endpoints for avatar services.
🛠️ Tip: Test connectivity to each endpoint using a simple
pingorcurlcommand to verify access before onboarding multiple users.