dns

Configure NetBird DNS nameservers, custom zones, and management modes.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/renne/skills --skill dns-renne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dns
Source: https://github.com/renne/skills/tree/main/netbird/dns
Command: npx skills add https://github.com/renne/skills --skill dns-renne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies and enhances DNS management within your NetBird network, ensuring seamless name resolution for internal resources and troubleshooting connectivity issues.

Core Features & Use Cases

  • Nameserver Configuration: Define primary and custom nameservers with specific match domains for split-horizon DNS.
  • Custom Zones: Host private DNS records (A, AAAA, CNAME) directly within NetBird without external DNS servers.
  • DNS Management Modes: Control whether NetBird manages DNS settings on peers (Managed) or leaves them untouched (Unmanaged).
  • Use Case: Configure NetBird to resolve internal service names like api.internal.company.com to their private IPs, while all other internet traffic uses your default public DNS.

Quick Start

Use the dns skill to configure a custom nameserver for the 'corp.local' domain.

Frequently Asked Questions about dns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure split-horizon DNS for internal domains in NetBird?

Split-horizon DNS is configured by defining primary and custom nameservers with specific match domains in NetBird. This setup resolves internal service names like api.internal.company.com to private IPs while routing other traffic to default public DNS.

Can I host private DNS records directly within NetBird without an external DNS server?

Yes, custom zones allow hosting private DNS records directly within NetBird without external DNS servers. You can create and manage A, AAAA, and CNAME records for your private network entirely inside the overlay.

What is the difference between managed and unmanaged DNS modes for NetBird peers?

Managed mode means NetBird controls DNS settings on peers, while unmanaged mode leaves them untouched. Choosing managed ensures NetBird automatically applies your configured nameservers and custom zones across the overlay network.

Why does DNS resolution fail for peers inside the NetBird overlay network?

DNS resolution fails when peer settings are unmanaged or custom zones lack proper A, AAAA, or CNAME records. Troubleshooting involves verifying nameserver configuration, checking search domains, and ensuring peers use managed DNS mode.

Do I need prior knowledge of DNS concepts to manage custom zones in NetBird?

Yes, managing custom zones requires understanding DNS concepts like A, AAAA, CNAME records, and search domains. This foundational knowledge is necessary to correctly configure private DNS records and troubleshoot resolution issues.