feat(domains): show user namespace in dashboard

src/components/DashboardComponents.jsx

@@ -1124,7 +1124,7 @@ export const DomainManager = ({ userId, username, servers, sendMessage, showAler
               </button>
             </div>
             <div className="p-6 space-y-6">
-              <SettingsPanel title="Domain Details" description={`Choose a unique subdomain. It will end with .${branding.domain}`}>
+              <SettingsPanel title="Domain Details" description={`Choose a name under u-${username}.${branding.domain}. Other names under your username are available too.`}>
                 <div className="space-y-4">
                   <div className="relative">
                     <input 
@@ -1136,7 +1136,7 @@ export const DomainManager = ({ userId, username, servers, sendMessage, showAler
                       style={{ color: colors.brightWhite }}
                     />
                     <div className="absolute right-3 top-1/2 -translate-y-1/2 text-xs font-black opacity-30 uppercase tracking-widest pointer-events-none">
-                      .{branding.domain}
+                      .u-{username}.{branding.domain}
                     </div>
                   </div>
                 </div>

src/pages/DocumentationPage.jsx

@@ -488,9 +488,9 @@ All servers deployed on ${branding.name} share a high-performance static IP but
 - **Example**: If your server is assigned port \`31452\`, you connect via \`85.237.179.121:31452\`.
 
 ## Subdomain System
-We provide automatic DNS management via the **deSEC API**.
+We provide DNS through the **deSEC API**. Each account uses the namespace \`u-{username}.${branding.domain}\`; names registered below it resolve through a wildcard CNAME to the platform domain.
 - **Format**: \`{label}.u-{username}.${branding.domain}\`
-- **SSL**: Automatic Let's Encrypt certificates are provisioned for all subdomains.
+- **DNS**: Wildcard DNS directs registered names to the platform edge. A DNS record alone does not connect a hostname to a service; link it to a website or VPS in the Domains tab.
 - **Custom Domains**: You can point your own domain (e.g., example.com) by creating an **A Record** pointing to \`85.237.179.121\`.`
         },
         {
@@ -766,25 +766,18 @@ Every user on ${branding.name} has their own personal network space based on the
 ## Linking to a Server
 Once a domain is created, you can "point" it to one of your active servers. 
 - If linked to a **Website**, it will automatically handle SSL (HTTPS).
-- If linked to a **Game Server**, you can join using the domain instead of the IP. (Note: You still need to provide the Port in the game client).`
+- If linked to a **Game Server**, the hostname resolves to the platform edge. You still need the assigned port in the game client; automatic port discovery is planned.`
         },
         {
           id: 'dnssec-warnings',
-          title: 'Resolving DNSSEC Warnings',
-          content: `# Fixing DNSSEC and NS Warnings
+          title: 'DNS and domain availability',
+          content: `# DNS and domain availability
 
-If you see a warning saying **"No NS records found for child domain"** or **"DNSSEC configuration issues"**, don't panic! 
+Platform subdomains inherit DNSSEC protection from the parent zone. You do not need to configure nameservers for an AnchorHost subdomain.
 
-## Why is this happening?
-${branding.name} uses high-security DNSSEC to protect your subdomains from being hijacked. For this to work, our main system needs to confirm that your specific "child" space is ready.
+New names resolve through wildcard DNS, but they still need to be registered in the Domains tab and linked to a compatible service before they serve an application. DNS changes can take time to reach resolvers that have cached an older answer.
 
-## How to Fix
-Usually, this is handled automatically within 5-10 minutes of creating your account. If the warning persists:
-1. Ensure you have at least one **Subdomain** registered in the Domains tab.
-2. If you are using a **Custom Domain** (e.g., \`mysite.com\`), you must point your Nameservers to:
-   - \`ns1.desec.io\`
-   - \`ns2.desec.org\`
-3. Wait for propagation (can take up to 24 hours).`
+For a custom domain, keep your current DNS provider and add the record shown during custom-domain setup. Do not move your nameservers unless you intend to transfer DNS management.`
         }
       ]
     },