Skip to main content

Dynamic DNS (DDNS) / URL Not Working

If your deployment's Dynamic DNS (DDNS) or URL is not working, it's likely because you haven't joined an organization. This guide explains why DDNS requires organization membership and how to resolve the issue.

Understanding the Issue​

Dynamic DNS (DDNS) / URL functionality is a feature that allows your deployments to be accessible via a consistent URL. However, this feature requires that you have joined an organization in the NuNet network.

What Works Without Organization Membership​

  • Deployments: You can still create and deploy ensembles
  • Local Deployments: Deployments to your local machine will work
  • Targeted Deployments: Deployments to specific peers can function
  • Untargeted Deployments: Network-selected deployments may work

What Doesn't Work Without Organization Membership​

  • DDNS/URL: Dynamic DNS URLs will not be enabled or functional
  • Persistent URLs: You won't get persistent URLs for your deployments
  • DNS Names: Custom DNS names configured in ensembles won't resolve

Why Organization Membership is Required​

Dynamic DNS functionality in NuNet requires organization membership because:

  1. Identity Management: Organizations provide the DID (Decentralized Identifier) and DMS context needed for DNS registration
  2. Capability Anchoring: DDNS capabilities are granted through organization roles
  3. Network Integration: DNS services are managed at the organization level
  4. Security and Governance: Organizations ensure proper access control for DNS resources

How to Fix the Issue​

Step 1: Verify Your Organization Status​

  1. Check Dashboard Status

    • Go to your NuNet Appliance dashboard
    • Look for the "Onboarding Status" indicator
    • If it shows "Not Onboarded", you need to join an organization

  2. Verify Organization Membership

    • Navigate to the Organizations section in the dashboard
    • Check if you're listed as a member of any organization
    • Confirm your membership status is active

Step 2: Join an Organization​

If you haven't joined an organization:

  1. Navigate to Organizations

    • In the NuNet Appliance dashboard, go to the Organizations section
    • Click Fetch Known Orgs to refresh the list

  2. Select an Organization

    • Choose an organization that aligns with your needs
    • Review the organization's requirements and policies

  3. Complete Onboarding

    • Fill out the onboarding form
    • Verify your email address
    • Wait for approval if required
    • Restart DMS when prompted

For detailed instructions, see Joining an Organization.

Step 3: Verify DDNS After Joining​

After joining an organization:

  1. Check Organization Status

    • Confirm your dashboard shows "Onboarded"
    • Verify you have the necessary roles and capabilities

  2. Restart DMS (if needed)

    • If prompted during onboarding, restart DMS
    • This ensures all capabilities are properly anchored

  3. Test Deployment with DDNS

    • Create a new deployment or check existing deployments
    • Configure a DNS name in your ensemble parameters
    • Verify the DDNS/URL is now available and working

Understanding Deployment Types and DDNS​

Local Deployments​

Local deployments may work without organization membership, but:

  • DDNS/URL will not be available
  • Access will be limited to local network methods (IP address)
  • No persistent URLs will be generated

Remote Deployments​

For remote deployments:

  • Targeted Deployments: May work but without DDNS
  • Untargeted Deployments: Network routing may work, but DDNS requires organization membership

Common Scenarios​

Scenario 1: Deployment Works but No URL​

Symptom: Your deployment is running successfully, but you don't see a URL or DDNS name.

Cause: You haven't joined an organization.

Solution: Join an organization to enable DDNS/URL functionality.

Scenario 2: DNS Name Parameter Ignored​

Symptom: You configure a DNS name in your ensemble parameters, but it's not working.

Cause: DDNS capabilities require organization membership.

Solution: Join an organization and redeploy with the DNS name parameter.

Scenario 3: Previous Deployments Lost DDNS​

Symptom: Deployments that previously had URLs no longer have working URLs.

Possible Causes:

  • You may have left an organization
  • Organization may have revoked DDNS capabilities
  • DMS may need to be restarted

Solution: Verify organization membership and restart DMS if needed.

Best Practices​

  1. Join Before Deploying: Join an organization before creating deployments that require DDNS
  2. Verify Status: Always check your onboarding status before expecting DDNS functionality
  3. Understand Requirements: Be aware that some features require organization membership
  4. Keep Membership Active: Maintain active organization membership for ongoing DDNS access

Getting Help​

If you've joined an organization but DDNS is still not working:

  1. Verify Organization Membership: Confirm you're actively onboarded
  2. Check Roles and Capabilities: Ensure your organization has granted DDNS capabilities
  3. Restart DMS: Try restarting DMS to refresh capabilities
  4. Contact Support: Reach out through the Support Process if issues persist