DNS - i dont get it

[stempfle]

Hey. So I just installed a brand new Raspberry PI 3 with the OS Lite and Docker.
OpenNova Server is running - but DNS is not.

I used this:
docker-compose.linux.yml and eddited the Target-IP to my Raspberry-IP 192.168.178.8
I also changed in my FritzBox the Network-Settings for DHCP to use 192.168.178.8 as DNS-Server.

Content of my compose in the first commend

any ideas?

Thanks :)

[stempfle]

# OpenNova Server — Linux production configuration with host networking.
#
# Op Linux gebruikt de container `network_mode: host` zodat:
#   - mDNS-multicast de LAN bereikt (mower auto-discovery via novabot.local)
#   - socket.remoteAddress het echte mower-IP teruggeeft (geen Docker NAT)
#   - de camera-proxy direct met de mower kan praten
#
# Quick start:
#   TARGET_IP=192.168.178.8 docker compose -f docker-compose.linux.yml up -d
#
# Poorten (80, 443, 1883, 5353/udp, optioneel 53/udp) worden direct op de
# host gebonden — zorg dat deze vrij zijn en de firewall ze toelaat.
#
# Admin: http://localhost/admin
# Provision devices: use the OpenNova app (iOS/Android) or bootstrap tool

services:
  opennova:
    image: rvbcrs/opennova:latest
    build: .
    container_name: opennova
    restart: unless-stopped
    network_mode: host          # Geen Docker NAT — echte client-IPs zichtbaar
                                # + mDNS multicast bereikt LAN
    environment:
      # Timezone — must match the timezone used by the app when creating schedules
      TZ: ${TZ:-Europe/Amsterdam}
      PORT: 80
      DB_PATH: /data/novabot.db
      STORAGE_PATH: /data/storage
      FIRMWARE_PATH: /data/firmware
      ENABLE_TLS: "true"

      # Tijdelijk: log iedere succesvolle JWT auth zodat we wisselende tokens kunnen tracen
      AUTH_DEBUG: "1"

      # Optional: enable web dashboard (default: disabled)
      ENABLE_DASHBOARD: "true"

      # Your server's LAN IP (for firmware download URLs, TLS cert SAN + DNS)
      TARGET_IP: 192.168.178.8

      # Proxy mode: 'local' (default) serves Novabot endpoints locally;
      # 'cloud' forwards every HTTP request to app.lfibot.com (debug).
      PROXY_MODE: ${PROXY_MODE:-local}

      # Optional: DNS redirect for Novabot app (requires TARGET_IP).
      # Maps mqtt.lfibot.com / app.lfibot.com → TARGET_IP so unmodified
      # stock app + firmware reach this server. Bind on host port 53/udp.
      # ENABLE_DNS: "true"
      UPSTREAM_DNS: ${UPSTREAM_DNS:-8.8.8.8}

      # Home Assistant MQTT bridge — auto-discover mowers + map images
      HA_MQTT_HOST: ${HA_MQTT_HOST:-}
      HA_MQTT_PORT: ${HA_MQTT_PORT:-1883}
      HA_MQTT_USER: ${HA_MQTT_USER:-}
      HA_MQTT_PASS: ${HA_MQTT_PASS:-}

      # Public base URL of the OpenNova server — needed so HA can fetch
      # the rendered map SVG via image entity. Without this the bridge
      # still publishes sensors but no image entity is discovered.
      RENDER_BASE_URL: ${RENDER_BASE_URL:-http://${TARGET_IP}}

      # Min interval (ms) between map image republishes. Default 15s
      # keeps HA responsive without spamming the broker.
      HA_MAP_THROTTLE_MS: ${HA_MAP_THROTTLE_MS:-15000}

      # ntfy.sh push notifications — set NTFY_TOPIC in .env to enable.
      # Topics are unauthenticated; pick something long and random.
      NTFY_TOPIC: ${NTFY_TOPIC:-}
      NTFY_URL: ${NTFY_URL:-https://ntfy.sh}
      NTFY_PRIORITY: ${NTFY_PRIORITY:-}

      # Optional: HA webhook trigger URL (full event JSON POSTed)
      HA_WEBHOOK_URL: ${HA_WEBHOOK_URL:-}

      # Battery % crossing point for the low_battery event
      LOW_BATTERY_THRESHOLD: ${LOW_BATTERY_THRESHOLD:-20}
    volumes:
      - ./data:/data

[dir26738]

in your docker file, try to remove the comment on line "# ENABLE_DNS: "true"

[stempfle]

that was the issue! Thanks! I Just copied from https://github.com/rvbcrs/Novabot/blob/master/docker-compose.linux.yml - my bad... :)

[stempfle]

Well - Mower and Base is "online" but still:

any idea about this issue? :)

[stempfle]

Fix: DNS redirect for app.lfibot.com / mqtt.lfibot.com (OpenNova)
🧩 Problem

The domains app.lfibot.com and mqtt.lfibot.com were not being redirected to the local Raspberry Pi (192.168.178.8) even though the PC was correctly using it as DNS. Instead, they resolved to an external IP (internet DNS).

🔍 Root cause

dnsmasq was running on the Raspberry Pi and handling DNS requests, but it had no domain override configuration. As a result, all queries were forwarded to upstream DNS servers instead of being redirected locally.

⚙️ Solution steps

1. Identify active DNS service
   sudo ss -ulpn | grep :53

→ showed: dnsmasq is bound to port 53

2. Check configuration structure
   /etc/dnsmasq.d/

→ directory did not exist (no modular config setup)

3. Add manual dnsmasq configuration
   sudo nano /etc/dnsmasq.conf

Added the following rules:

address=/app.lfibot.com/192.168.178.8
address=/mqtt.lfibot.com/192.168.178.8

4. Restart DNS service

Since no systemd service was available:

sudo reboot

✅ Result
app.lfibot.com → 192.168.178.8
mqtt.lfibot.com → 192.168.178.8
Local DNS redirection now works correctly

🧠 Key takeaway
The fix was to manually configure dnsmasq with domain override rules, because OpenNova’s DNS redirection was not active and no /etc/dnsmasq.d configuration structure existed.