Merge pull request #28 from tuanductran/copilot/add-integration-categories

Author: tuanductran

skills/integrations/SKILL.md

@@ -13,9 +13,13 @@ metadata:
 
 | Rule | Keywords | Description |
 |------|----------|-------------|
+| [Browser Native DoH Configuration](rules/browsers.md) | browser, chrome, edge, firefox, doh, dns-over-https, secure-dns, encrypted-dns, corporate, proxy | Configure DNS-over-HTTPS directly in browsers for encrypted DNS without system-wide changes or admin privileges |
 | [DNSMasq Integration](rules/dnsmasq-integration.md) | dnsmasq, dns, router, client reporting, conditional configuration, port configuration, setup-router | Configure DNSMasq and NextDNS to run together while maintaining client reporting and conditional configuration features |
-| [Public DNS and AdGuard Home Integration](rules/public-dns-and-adguard.md) | public dns, adguard, anycast, doh, dot, browser setup, windows, android, ios, upstream dns, bootstrap dns | Configure NextDNS public DNS servers on browsers and operating systems, and integrate with AdGuard Home as upstream DNS provider |
+| [Mobile Native Encrypted DNS Configuration](rules/mobile-native.md) | mobile, android, ios, iphone, ipad, private-dns, dot, dns-over-tls, configuration-profile, mobileconfig, native, lightweight | Configure native encrypted DNS on Android and iOS devices without battery-draining background apps |
 | [OpenWrt Integration](rules/openwrt.md) | openwrt, router, installation, upgrade, troubleshooting, ssh, luci | Installation, upgrade, and troubleshooting guidance for NextDNS on OpenWrt routers |
+| [pfSense and OPNsense Integration](rules/pfsense-opnsense.md) | pfsense, opnsense, firewall, router, unbound, dns-over-tls, dot, freebsd, dns resolver | Deploy NextDNS on pfSense and OPNsense firewalls with proper encrypted DNS configuration and platform-specific guidance |
+| [Public DNS and AdGuard Home Integration](rules/public-dns-and-adguard.md) | public dns, adguard, anycast, doh, dot, browser setup, windows, android, ios, upstream dns, bootstrap dns | Configure NextDNS public DNS servers on browsers and operating systems, and integrate with AdGuard Home as upstream DNS provider |
+| [Synology Integration (DSM and SRM)](rules/synology.md) | synology, dsm, srm, nas, router, ssh, cli, dhcp, network | Install NextDNS on Synology NAS (DSM) and routers (SRM) with proper SSH access and network configuration |
 
 ## Efficiency Rules
 

skills/integrations/rules/browsers.md

@@ -0,0 +1,213 @@
+---
+title: Browser Native DoH Configuration
+impact: MEDIUM
+impactDescription: Configuring DNS-over-HTTPS directly in browsers enables encrypted DNS without system-wide changes or requiring administrator privileges. Without this guidance, users in restricted environments may be unable to leverage NextDNS protection when software installation is blocked.
+type: capability
+tags: browser, chrome, edge, firefox, doh, dns-over-https, secure-dns, encrypted-dns, corporate, proxy
+---
+
+# Browser Native DoH Configuration
+
+**Impact: MEDIUM** - Enables NextDNS protection in restricted environments without system-wide changes or administrative privileges
+
+Modern browsers include built-in support for DNS-over-HTTPS (DoH), allowing encrypted DNS queries without installing additional software or requiring system administrator rights. This is particularly useful in corporate, educational, or restrictive network environments.
+
+## Use Cases
+
+### When to Use Browser-Level DoH
+
+- **Corporate Networks**: When IT policies block software installation or system-wide DNS changes
+- **Shared Computers**: Public libraries, internet cafes, or shared workstations
+- **Restrictive Firewalls**: Networks that block standard DNS (port 53) but allow HTTPS (port 443)
+- **Quick Setup**: No system configuration or administrative access required
+- **Testing**: Verify NextDNS configuration before deploying system-wide
+- **User-Specific Protection**: Different users on the same computer can have different DNS settings
+
+### Limitations
+
+- **Browser-only**: Only protects DNS queries from the browser itself, not other applications
+- **Per-browser**: Must be configured separately in each browser
+- **Profile-dependent**: Settings may not sync across devices unless using browser sync
+
+## Chrome and Edge Configuration
+
+Google Chrome and Microsoft Edge share the same Chromium-based architecture and use identical configuration steps.
+
+### Configuration Steps
+
+1. Open browser settings:
+    - **Chrome**: `chrome://settings/security`
+    - **Edge**: `edge://settings/privacy`
+
+2. Navigate to:
+    - **Privacy and security** → **Security**
+
+3. Scroll to **Advanced** section
+
+4. Locate **Use secure DNS** setting
+
+5. Enable the toggle switch
+
+6. Select **With: Custom**
+
+7. Enter your NextDNS DoH URL:
+    ```text
+    https://dns.nextdns.io/<config_id>
+    ```
+    Replace `<config_id>` with your actual NextDNS Configuration ID
+
+8. Click **Save** or close settings (changes apply automatically)
+
+### Finding Your Configuration ID
+
+1. Log in to [https://my.nextdns.io](https://my.nextdns.io)
+2. Select your configuration
+3. Your Configuration ID is displayed in the URL: `https://my.nextdns.io/<config_id>/setup`
+4. The ID is a 6-character alphanumeric string (e.g., `abc123`)
+
+### Visual Path Reference
+
+```text
+Settings
+  └─ Privacy and security
+       └─ Security
+            └─ Advanced
+                 └─ Use secure DNS
+                      └─ With: Custom
+                           └─ Enter custom provider
+```
+
+## Firefox Configuration
+
+Firefox has its own implementation of DNS-over-HTTPS with slightly different terminology.
+
+### Configuration Steps
+
+1. Open browser settings:
+    - Navigate to `about:preferences#privacy`
+    - Or go to **Settings** → **Privacy & Security**
+
+2. Scroll to **DNS over HTTPS** section
+
+3. Select **Max Protection** (recommended)
+    - Alternative: **Increased Protection** (falls back to regular DNS if DoH fails)
+
+4. In the dropdown, select **Custom**
+
+5. Enter your NextDNS DoH URL:
+    ```text
+    https://dns.nextdns.io/<config_id>
+    ```
+    Replace `<config_id>` with your actual NextDNS Configuration ID
+
+6. Changes apply automatically
+
+### Visual Path Reference
+
+```text
+Settings
+  └─ Privacy & Security
+       └─ DNS over HTTPS
+            └─ Max Protection
+                 └─ Choose provider
+                      └─ Custom
+                           └─ Enter custom DNS URL
+```
+
+### Firefox Protection Modes
+
+| Mode | Behavior | Use Case |
+|------|----------|----------|
+| **Max Protection** | Always use DoH, fail if unavailable | Best security, recommended |
+| **Increased Protection** | Use DoH, fallback to regular DNS | Compatibility with problematic networks |
+| **Off** | Disable DoH | Troubleshooting only |
+
+## Verification
+
+After configuration, verify that DoH is working correctly:
+
+### Method 1: NextDNS Test Page
+
+1. Visit [https://test.nextdns.io](https://test.nextdns.io)
+2. You should see:
+    - ✓ **Protocol**: HTTPS (DoH)
+    - ✓ **Status**: Connected
+    - ✓ **Configuration ID**: Your config ID
+
+### Method 2: Browser Network Tools
+
+#### Chrome/Edge
+1. Open DevTools (F12)
+2. Navigate to **Network** tab
+3. Filter by **Type: DNS**
+4. Reload a webpage
+5. Verify DNS queries are going to `dns.nextdns.io`
+
+#### Firefox
+1. Type `about:networking#dns` in the address bar
+2. Check the **TRR** (Trusted Recursive Resolver) status
+3. Should show as "TRR only" for Max Protection
+
+### Method 3: Check Query Logs
+
+1. Log in to [https://my.nextdns.io](https://my.nextdns.io)
+2. Navigate to **Logs** tab
+3. Browse the web and verify queries appear in real-time
+
+## Troubleshooting
+
+### DoH Not Working
+
+**Possible causes:**
+
+1. **Incorrect Configuration ID**: Double-check your ID from the NextDNS dashboard
+2. **Typo in URL**: Ensure the URL is `https://dns.nextdns.io/<config_id>` (no trailing slash)
+3. **Network Blocking**: Some networks may block DoH traffic (port 443 to dns.nextdns.io)
+4. **Browser Sync Conflict**: Disable browser sync temporarily to rule out conflicts
+
+### Testing Fallback
+
+Temporarily use an invalid configuration ID to verify the browser is actually using DoH:
+
+```text
+https://dns.nextdns.io/invalid
+```
+
+If you can't browse, DoH is working (browser is not falling back to regular DNS).
+
+### Corporate Proxy Issues
+
+Some corporate proxies inspect HTTPS traffic:
+
+- **Symptoms**: Certificate errors, DoH not working
+- **Solutions**:
+    - Check with IT department about SSL/TLS inspection policies
+    - Use Firefox with **Increased Protection** mode (allows fallback)
+    - Consider using the NextDNS app on personal devices instead
+
+## Comparison with System-Wide Configuration
+
+| Feature | Browser DoH | System-Wide NextDNS |
+|---------|-------------|---------------------|
+| **Admin Rights** | ❌ Not required | ✅ Required |
+| **Coverage** | Browser only | All applications |
+| **Setup Time** | < 1 minute | 5-10 minutes |
+| **Device Analytics** | ❌ Not available | ✅ Full analytics |
+| **Per-User Config** | ✅ Yes | ❌ Shared |
+| **Corporate Networks** | ✅ Usually works | ⚠️ May be blocked |
+
+## Best Practices
+
+- **Use Max Protection in Firefox** for the strongest security posture
+- **Test before deploying**: Visit test.nextdns.io to verify configuration
+- **Document your setup**: Keep a record of which browsers are configured
+- **Combine with extensions**: Use with privacy extensions for enhanced protection
+- **Check logs regularly**: Monitor NextDNS dashboard to ensure queries are being processed
+- **Consider system-wide for personal devices**: Browser-level DoH is best for restricted environments
+
+## Reference
+
+- [Chrome Secure DNS Documentation](https://www.chromium.org/developers/dns-over-https)
+- [Firefox DNS-over-HTTPS Guide](https://support.mozilla.org/kb/firefox-dns-over-https)
+- [NextDNS Setup Guide](https://help.nextdns.io)
+- [DNS-over-HTTPS (RFC 8484)](https://datatracker.ietf.org/doc/html/rfc8484)