Package: aardvark-dns
Version: 1.4.0-3
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
* What led up to the situation?
apt upgrade on current 13.6 debian caused application in containers not
to work.
Logs show application had problem resolving given URL, e.g.
https://auth.tesla.com
* What exactly did you do (or not do) that was effective (or
ineffective)?
I tried to bump current 1.14.0-3 version to 1.17.1-2, didn't help.
* What was the outcome of this action?
Same error as with current 1.14.0-3 version.
I tried to revert it back to older version, 1.4.0-3, which seems to fix
the issue.
* What outcome did you expect instead?
That URL would be resolvable.
I did however downgrade the package to 1.4.0-3 which solved the issue.
My setup:
This is a VM on proxmox cluster on the same network where router/DNS server is.
Host is using this DNS directly.
podman containers are built with compose script exactly as specified on project
page:
https://docs.teslamate.org/docs/installation/docker
Example of an actual application log (VIN redacted):
2026-08-03 17:56:58.631 [error] GET
https://owner-api.teslamotors.com/api/1/vehicles/<redacted> -> error:
%Finch.TransportError{reason: :nxdomain, source: %Mint.TransportError{reason:
:nxdomain}} (8001.874 ms)
Testing within host:
$ sudo nsenter -t $(podman inspect -f '{{.State.Pid}}' teslamate_teslamate_1)
-n -- nslookup auth.tesla.com 10.89.0.1
;; communications error to 10.89.0.1#53: timed out
^C
Once I downgraded to aardvark-dns_1.4.0-3 it started to work again:
$ sudo nsenter -t $(podman inspect -f '{{.State.Pid}}' teslamate_teslamate_1)
-n -- nslookup auth.tesla.com 10.89.0.1
Server: 10.89.0.1
Address: 10.89.0.1#53
Non-authoritative answer:
auth.tesla.com canonical name = auth.tesla.com.edgekey.net.
auth.tesla.com.edgekey.net canonical name = e1792.dscx.akamaiedge.net.
Name: e1792.dscx.akamaiedge.net
Address: 2.22.112.66
..
During testing if I used TCP it worked (used pid of container directly here):
$ sudo nsenter -t 10438 -n -- nslookup -vc auth.tesla.com 10.89.0.1
Server: 10.89.0.1
Address: 10.89.0.1#53
Non-authoritative answer:
auth.tesla.com canonical name = auth.tesla.com.edgekey.net.
..
..
As mentioned in subject not all DNS queries had problems.
Example of working query:
$ sudo nsenter -t 5602 -n -- nslookup sme.sk 10.89.0.1
Server: 10.89.0.1
Address: 10.89.0.1#53
Non-authoritative answer:
Name: sme.sk
Address: 172.66.145.92
..
Currently using:
# dpkg -l |grep -E 'aard|neta'
iU aardvark-dns 1.4.0-3
amd64 Container-focused DNS server
ii netavark 1.14.0-2
amd64 Rust based network stack for containers
-- System Information:
Debian Release: 13.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.100+deb13-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages aardvark-dns depends on:
ii libc6 2.41-12+deb13u3
ii libgcc-s1 14.2.0-19
ii netavark 1.14.0-2
aardvark-dns recommends no packages.
aardvark-dns suggests no packages.
-- no debconf information
