Start free trial
Foldr only resolves fully qualified hostnames · Self-hosted

Foldr only resolves fully qualified hostnames

Updated 4 May 2026 Server Deployment Self-hosted only

Foldr only resolves fully qualified hostnames

Symptom

From the appliance, fully qualified names resolve correctly:

$ ping fileserver.example.local
PING fileserver.example.local ... 64 bytes from 10.0.1.20

But short names don’t:

$ ping fileserver
ping: fileserver: Name or service not known

This breaks anywhere Foldr expects a short hostname to work, including some SMB share definitions and LDAP referrals.

Cause

The appliance builds its DNS search domain from its own hostname. If the hostname is set to a bare label like foldr, no search domain is added and short-name lookups have nothing to append. If the hostname is set to a fully qualified name like foldr.example.local, the suffix example.local becomes the search domain and short names resolve correctly against it.

You can confirm what the appliance is currently using:

$ show-resolv-conf
nameserver 10.0.1.10
nameserver 10.0.1.11
search example.local

If the search line is missing or contains the wrong domain, this is your problem.

Fix

Set the appliance hostname to a fully qualified name in your internal domain. From Foldr Settings:

  1. Sign in to Foldr Settings as fadmin.
  2. Open Network settings.
  3. Set the hostname to <short-name>.<internal-domain>, for example foldr.example.local.
  4. Save and reboot the appliance for the change to take effect.

After the reboot, show-resolv-conf should list your internal domain on the search line, and short-name lookups will work.

← All articles