starred/dns-proxy-server-mageddo

Fork 0

mirror of https://github.com/mageddo/dns-proxy-server.git synced 2026-04-25 17:35:54 +03:00

[GH-ISSUE #429] random IPv6 of some other container is returned if proper IPv6 does not exist #152

New issue

Closed

opened 2026-02-26 04:34:12 +03:00 by kerem · 8 comments

kerem commented

2026-02-26 04:34:12 +03:00

Owner

Originally created by @pschiffe on GitHub (Dec 16, 2023).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/429

What is Happening / What is expected

It's visible in the log:

19:20:38.793 [Thread-29      ] DEB c.m.d.server.dns.RequestHandlerDefault            l=48   m=solve                           status=solveReq, kind=udp, query=query=AAAA:plausible.docker
19:20:38.828 [Thread-29      ] DEB c.m.dnsproxyserver.docker.ContainerSolvingService l=90   m=findBestIpMatch                 status=networkNotFoundForContainer, name=dps
19:20:38.828 [Thread-29      ] DEB c.m.dnsproxyserver.docker.ContainerSolvingService l=90   m=findBestIpMatch                 status=networkNotFoundForContainer, name=bridge
19:20:38.828 [Thread-29      ] DEB c.m.dnsproxyserver.docker.ContainerSolvingService l=100  m=findBestIpMatch                 status=predefinedNetworkNotFound, action=findSecondOption, searchedNetworks=[dps, bridge], container=/plausible
19:20:38.829 [Thread-29      ] DEB c.m.dnsproxyserver.docker.DockerNetworkDAODefault l=53   m=findByName                      queryName=plausible, foundName=plausible
19:20:38.829 [Thread-29      ] DEB c.m.dnsproxyserver.docker.ContainerSolvingService l=120  m=lambda$findBestIpMatch$3        status=foundIp, networks=[plausible], networkName=plausible, driver=bridge, foundIp=null
19:20:38.834 [Thread-29      ] DEB c.mageddo.dnsproxyserver.docker.DockerDAODefault  l=64   m=findBestNetwork                 status=bestNetwork, network=phpmyadmin, ip=172.19.0.1
19:20:38.834 [Thread-29      ] DEB c.m.dnsproxyserver.docker.ContainerSolvingService l=132  m=lambda$findBestIpMatch$4        status=noNetworkAvailable, usingHostMachineIp=fddb:21e4:36d4:1:0:0:0:1
19:20:38.834 [Thread-29      ] DEB c.m.d.server.dns.RequestHandlerDefault            l=87   m=solve0                          status=solved, currentSolverTime=40, totalTime=40, solver=SolverDocker, req=query=AAAA:plausible.docker, res=rc=0, res=plausible.docker.  30  IN  AAAA  fddb:21e4:36d4:1:0:0:0:1
19:20:38.834 [Thread-29      ] DEB c.m.d.server.dns.RequestHandlerDefault            l=102  m=solve0                          status=solveSummary, summary=[(SolverSystem,0), (SolverDocker,40)]
19:20:38.834 [Thread-29      ] DEB c.m.dnsproxyserver.server.dns.solver.SolverCache  l=44   m=lambda$handleRes$0              status=hotload, k=AAAA-plausible.docker, ttl=PT30S, simpleMsg=query=AAAA:plausible.docker
19:20:38.834 [Thread-29      ] DEB c.m.d.server.dns.RequestHandlerDefault            l=53   m=solve                           status=solveRes, kind=udp, time=41, res=rc=0, res=plausible.docker.  30  IN  AAAA  fddb:21e4:36d4:1:0:0:0:1, req=query=AAAA:plausible.docker
19:20:38.835 [Thread-29      ] DEB com.mageddo.dnsproxyserver.server.dns.UDPServer   l=58   m=handle                          status=success, query=query=AAAA:plausible.docker, res=rc=0, res=plausible.docker.  30  IN  AAAA  fddb:21e4:36d4:1:0:0:0:1, serverAddr=/0:0:0:0:0:0:0:0, clientAddr=/127.0.0.1:50714, dataLength=512, datagramLength=45

findBestNetwork chose phpmyadmin network, but plausible is not connected to this network:

m=findBestNetwork                 status=bestNetwork, network=phpmyadmin, ip=172.19.0.1

plausible doesn't have IPv6 enabled (plausible doesn't support dual-stack):

# docker network inspect plausible
[
    {
        "Name": "plausible",
        "Id": "befd81d511296c5ab4efc42c9c5aad8bae01699b8412a84e4d4b60cc3c60da69",
        "Created": "2023-12-15T23:13:19.226642613Z",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.23.0.0/16",
                    "Gateway": "172.23.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "3620250dbecb269fbdcafd08ca51e74a12c0b0e9736c339b08f3604df049ae31": {
                "Name": "plausible",
                "EndpointID": "854e197f641535077f2ef5390c5a7d0206ddfcf25ee02ab6831619a368c9c6d0",
                "MacAddress": "02:42:ac:17:00:03",
                "IPv4Address": "172.23.0.3/16",
                "IPv6Address": ""
            },
            "958b6568547a61345c4ba0931601364a2013dbc7898439632a1f323b549bd6f2": {
                "Name": "plausible-clickhouse",
                "EndpointID": "dcb1fc9049ad8ac9d2db4dd95ac1f3d5f465937bfde515c826d9cb028cee969e",
                "MacAddress": "02:42:ac:17:00:02",
                "IPv4Address": "172.23.0.2/16",
                "IPv6Address": ""
            }
        },
        "Options": {},
        "Labels": {}
    }
]

# docker network inspect phpmyadmin
[
    {
        "Name": "phpmyadmin",
        "Id": "282a7736c6b1cd6a3272b63828f40d91602b63707b4fefb95c5568429049c462",
        "Created": "2023-09-22T19:11:51.523662906Z",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": true,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.19.0.0/16",
                    "Gateway": "172.19.0.1"
                },
                {
                    "Subnet": "fddb:21e4:36d4:1::/64",
                    "Gateway": "fddb:21e4:36d4:1::1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "b175163001f4b77a976cd0a334bca0a84f52879360c64a859e5a509a33c0996c": {
                "Name": "phpmyadmin",
                "EndpointID": "c654415449e487868084bf3d1cca07190f89012927cef0dc9f1b026aa7506823",
                "MacAddress": "02:42:ac:13:00:02",
                "IPv4Address": "172.19.0.2/16",
                "IPv6Address": "fddb:21e4:36d4:1::2/64"
            }
        },
        "Options": {},
        "Labels": {}
    }
]

Specs

OS: 6.6.6-100.fc38.aarch64
Docker Version:

# docker version
Client:
 Version:           24.0.5
 API version:       1.43
 Go version:        go1.20.7
 Git commit:        %{shortcommit_cli}
 Built:             Sun Aug 27 16:45:35 2023
 OS/Arch:           linux/arm64
 Context:           default

Server:
 Engine:
  Version:          24.0.5
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.7
  Git commit:       %{shortcommit_moby}
  Built:            Sun Aug 27 16:45:35 2023
  OS/Arch:          linux/arm64
  Experimental:     true
 containerd:
  Version:          1.6.19
  GitCommit:        
 runc:
  Version:          1.1.8
  GitCommit:        
 docker-init:
  Version:          0.19.0
  GitCommit:

DPS Version: 3.15.13-snapshot

Originally created by @pschiffe on GitHub (Dec 16, 2023). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/429 ### What is Happening / What is expected It's visible in the log: ``` 19:20:38.793 [Thread-29 ] DEB c.m.d.server.dns.RequestHandlerDefault l=48 m=solve status=solveReq, kind=udp, query=query=AAAA:plausible.docker 19:20:38.828 [Thread-29 ] DEB c.m.dnsproxyserver.docker.ContainerSolvingService l=90 m=findBestIpMatch status=networkNotFoundForContainer, name=dps 19:20:38.828 [Thread-29 ] DEB c.m.dnsproxyserver.docker.ContainerSolvingService l=90 m=findBestIpMatch status=networkNotFoundForContainer, name=bridge 19:20:38.828 [Thread-29 ] DEB c.m.dnsproxyserver.docker.ContainerSolvingService l=100 m=findBestIpMatch status=predefinedNetworkNotFound, action=findSecondOption, searchedNetworks=[dps, bridge], container=/plausible 19:20:38.829 [Thread-29 ] DEB c.m.dnsproxyserver.docker.DockerNetworkDAODefault l=53 m=findByName queryName=plausible, foundName=plausible 19:20:38.829 [Thread-29 ] DEB c.m.dnsproxyserver.docker.ContainerSolvingService l=120 m=lambda$findBestIpMatch$3 status=foundIp, networks=[plausible], networkName=plausible, driver=bridge, foundIp=null 19:20:38.834 [Thread-29 ] DEB c.mageddo.dnsproxyserver.docker.DockerDAODefault l=64 m=findBestNetwork status=bestNetwork, network=phpmyadmin, ip=172.19.0.1 19:20:38.834 [Thread-29 ] DEB c.m.dnsproxyserver.docker.ContainerSolvingService l=132 m=lambda$findBestIpMatch$4 status=noNetworkAvailable, usingHostMachineIp=fddb:21e4:36d4:1:0:0:0:1 19:20:38.834 [Thread-29 ] DEB c.m.d.server.dns.RequestHandlerDefault l=87 m=solve0 status=solved, currentSolverTime=40, totalTime=40, solver=SolverDocker, req=query=AAAA:plausible.docker, res=rc=0, res=plausible.docker. 30 IN AAAA fddb:21e4:36d4:1:0:0:0:1 19:20:38.834 [Thread-29 ] DEB c.m.d.server.dns.RequestHandlerDefault l=102 m=solve0 status=solveSummary, summary=[(SolverSystem,0), (SolverDocker,40)] 19:20:38.834 [Thread-29 ] DEB c.m.dnsproxyserver.server.dns.solver.SolverCache l=44 m=lambda$handleRes$0 status=hotload, k=AAAA-plausible.docker, ttl=PT30S, simpleMsg=query=AAAA:plausible.docker 19:20:38.834 [Thread-29 ] DEB c.m.d.server.dns.RequestHandlerDefault l=53 m=solve status=solveRes, kind=udp, time=41, res=rc=0, res=plausible.docker. 30 IN AAAA fddb:21e4:36d4:1:0:0:0:1, req=query=AAAA:plausible.docker 19:20:38.835 [Thread-29 ] DEB com.mageddo.dnsproxyserver.server.dns.UDPServer l=58 m=handle status=success, query=query=AAAA:plausible.docker, res=rc=0, res=plausible.docker. 30 IN AAAA fddb:21e4:36d4:1:0:0:0:1, serverAddr=/0:0:0:0:0:0:0:0, clientAddr=/127.0.0.1:50714, dataLength=512, datagramLength=45 ``` `findBestNetwork` chose `phpmyadmin` network, but `plausible` is not connected to this network: ``` m=findBestNetwork status=bestNetwork, network=phpmyadmin, ip=172.19.0.1 ``` `plausible` doesn't have IPv6 enabled (plausible doesn't support dual-stack): ``` # docker network inspect plausible [ { "Name": "plausible", "Id": "befd81d511296c5ab4efc42c9c5aad8bae01699b8412a84e4d4b60cc3c60da69", "Created": "2023-12-15T23:13:19.226642613Z", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": null, "Config": [ { "Subnet": "172.23.0.0/16", "Gateway": "172.23.0.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "3620250dbecb269fbdcafd08ca51e74a12c0b0e9736c339b08f3604df049ae31": { "Name": "plausible", "EndpointID": "854e197f641535077f2ef5390c5a7d0206ddfcf25ee02ab6831619a368c9c6d0", "MacAddress": "02:42:ac:17:00:03", "IPv4Address": "172.23.0.3/16", "IPv6Address": "" }, "958b6568547a61345c4ba0931601364a2013dbc7898439632a1f323b549bd6f2": { "Name": "plausible-clickhouse", "EndpointID": "dcb1fc9049ad8ac9d2db4dd95ac1f3d5f465937bfde515c826d9cb028cee969e", "MacAddress": "02:42:ac:17:00:02", "IPv4Address": "172.23.0.2/16", "IPv6Address": "" } }, "Options": {}, "Labels": {} } ] ``` ``` # docker network inspect phpmyadmin [ { "Name": "phpmyadmin", "Id": "282a7736c6b1cd6a3272b63828f40d91602b63707b4fefb95c5568429049c462", "Created": "2023-09-22T19:11:51.523662906Z", "Scope": "local", "Driver": "bridge", "EnableIPv6": true, "IPAM": { "Driver": "default", "Options": null, "Config": [ { "Subnet": "172.19.0.0/16", "Gateway": "172.19.0.1" }, { "Subnet": "fddb:21e4:36d4:1::/64", "Gateway": "fddb:21e4:36d4:1::1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "b175163001f4b77a976cd0a334bca0a84f52879360c64a859e5a509a33c0996c": { "Name": "phpmyadmin", "EndpointID": "c654415449e487868084bf3d1cca07190f89012927cef0dc9f1b026aa7506823", "MacAddress": "02:42:ac:13:00:02", "IPv4Address": "172.19.0.2/16", "IPv6Address": "fddb:21e4:36d4:1::2/64" } }, "Options": {}, "Labels": {} } ] ``` ### Specs * OS: 6.6.6-100.fc38.aarch64 * Docker Version: ``` # docker version Client: Version: 24.0.5 API version: 1.43 Go version: go1.20.7 Git commit: %{shortcommit_cli} Built: Sun Aug 27 16:45:35 2023 OS/Arch: linux/arm64 Context: default Server: Engine: Version: 24.0.5 API version: 1.43 (minimum version 1.12) Go version: go1.20.7 Git commit: %{shortcommit_moby} Built: Sun Aug 27 16:45:35 2023 OS/Arch: linux/arm64 Experimental: true containerd: Version: 1.6.19 GitCommit: runc: Version: 1.1.8 GitCommit: docker-init: Version: 0.19.0 GitCommit: ``` * DPS Version: `3.15.13-snapshot`

kerem

2026-02-26 04:34:12 +03:00

closed this issue
added the
feature-request
label

kerem commented

2026-02-26 04:34:13 +03:00

Author

Owner

@mageddo commented on GitHub (Apr 23, 2024):

Hey @pschiffe , I can see behavior that might be not wanted but different of what your reported.

Looks like DPS didn't use phpmyadmin network but answered the hostmachine IPV6 IP, the thing is, like you said, none of "plausible" container connected networks has support for IPV6, so maybe it doesn't makes sense to answer the hostmachine IP.

I will have to think in the use cases related to use hostmachine IP to check if this behavior can be considered was wanted or not, maybe it can be a togglable feature.

@mageddo commented on GitHub (Apr 23, 2024): Hey @pschiffe , I can see behavior that might be not wanted but different of what your reported. Looks like DPS didn't use phpmyadmin network but answered the hostmachine IPV6 IP, the thing is, like you said, none of "plausible" container connected networks has support for IPV6, so maybe it doesn't makes sense to answer the hostmachine IP. I will have to think in the use cases related to use hostmachine IP to check if this behavior can be considered was wanted or not, maybe it can be a togglable feature.

kerem commented

2026-02-26 04:34:13 +03:00

Author

Owner

@pschiffe commented on GitHub (Apr 24, 2024):

I see, thanks for taking a look. You are right, the phpmyadmin has IP fddb:21e4:36d4:1::2, and the host has fddb:21e4:36d4:1::1 (which is returned by the dns proxy).

Returning the host IP in this case is useful only if the ports of the container are exposed to the host I think. Otherwise it's just a wrong answer. I think the correct behavior (at least that I would expect) is to return nothing, so the client can try for A record. Some clients on IPv6 enabled systems go for AAAA record first, and try for A only if AAAA is missing.

@pschiffe commented on GitHub (Apr 24, 2024): I see, thanks for taking a look. You are right, the phpmyadmin has IP `fddb:21e4:36d4:1::2`, and the host has `fddb:21e4:36d4:1::1` (which is returned by the dns proxy). Returning the host IP in this case is useful only if the ports of the container are exposed to the host I think. Otherwise it's just a wrong answer. I think the correct behavior (at least that I would expect) is to return nothing, so the client can try for A record. Some clients on IPv6 enabled systems go for AAAA record first, and try for A only if AAAA is missing.

kerem commented

2026-02-26 04:34:13 +03:00

Author

Owner

@mageddo commented on GitHub (May 2, 2024):

I've mapped returning the host IP in this case useful when:

If the ports of the container are exposed to the host and there are no networks in the container or all the container networks are not in bridge mode (it happens when the container is executed using docker-compose, bridge networks are dropped in this case.
When the container is running in network mode = host
-- updated --

@mageddo commented on GitHub (May 2, 2024): I've mapped returning the host IP in this case useful when: * If the ports of the container are exposed to the host and there are no networks in the container or all the container networks are not in bridge mode (it happens when the container is executed using docker-compose, bridge networks are dropped in this case. * When the container is running in network mode = host -- updated --

kerem commented

2026-02-26 04:34:13 +03:00

Author

Owner

@mageddo commented on GitHub (May 2, 2024):

@pschiffe please let me know if that solution can fix your unexpected behavior scenario

Try to identify the wanted and unwanted scenario automatically

If the container it's not in network mode = host and have not published ports then it makes no sense to answer the host IP address, do return no IP instead (NXDOMAIN).

@mageddo commented on GitHub (May 2, 2024): @pschiffe please let me know if that solution can fix your unexpected behavior scenario > ### Try to identify the wanted and unwanted scenario automatically > > If the container it's not in network mode = host and have not published ports then it makes no sense to answer the host IP address, do return no IP instead (NXDOMAIN).

kerem commented

2026-02-26 04:34:13 +03:00

Author

Owner

@pschiffe commented on GitHub (May 2, 2024):

have not published ports

this may not be good enough - for example, you expose one port for the web server, but not the other one for metrics, which you will gather only via container.docker name.

I have it like that in my setup, where grafana agent is running on the host and doing autodiscovery of container metrics via docker labels. As it's on the host, it's using dns proxy to resolve the IP of the containers.

It's true that most of the containers don't have ports exposed to the host, but there are ones like traefik proxy, and internal tools which have. Also for this to be a problem, these containers must have IPv6 missing, but there is still sw where dual stack is a problem.

Anyway, in general, I like the automagic feature, but it probably would be a good idea to be able to enforce the behavior with feature toggle as well :)

BTW, thanks for the great job!

@pschiffe commented on GitHub (May 2, 2024): > have not published ports this may not be good enough - for example, you expose one port for the web server, but not the other one for metrics, which you will gather only via `container.docker` name. I have it like that in my setup, where [grafana agent](https://grafana.com/docs/agent/latest/) is running on the host and doing autodiscovery of container metrics via docker labels. As it's on the host, it's using dns proxy to resolve the IP of the containers. It's true that most of the containers don't have ports exposed to the host, but there are ones like traefik proxy, and internal tools which have. Also for this to be a problem, these containers must have IPv6 missing, but there is still sw where dual stack is a problem. Anyway, in general, I like the automagic feature, but it probably would be a good idea to be able to enforce the behavior with feature toggle as well :) BTW, thanks for the great job!

kerem commented

2026-02-26 04:34:13 +03:00

Author

Owner

@mageddo commented on GitHub (May 2, 2024):

Thanks for the feedback. I will work on the feature toggle then.

@mageddo commented on GitHub (May 2, 2024): Thanks for the feedback. I will work on the feature toggle then.

kerem commented

2026-02-26 04:34:13 +03:00

Author

Owner

@mageddo commented on GitHub (May 8, 2024):

Hey @pschiffe 3.17.0-snapshot is being released, I would appreciate if you could check it out.

@mageddo commented on GitHub (May 8, 2024): Hey @pschiffe `3.17.0-snapshot` is being released, I would appreciate if you could check it out.

kerem commented

2026-02-26 04:34:13 +03:00

Author

Owner

@pschiffe commented on GitHub (May 8, 2024):

Very nice, seems to work great! Before:

# dig plausible.docker @127.0.0.1 -p 5300 aaaa
;; Warning: Client COOKIE mismatch

; <<>> DiG 9.19.18 <<>> plausible.docker @127.0.0.1 -p 5300 aaaa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7124
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 068f60a9251b2d84 (bad)
;; QUESTION SECTION:
;plausible.docker.		IN	AAAA

;; ANSWER SECTION:
plausible.docker.	30	IN	AAAA	fddb:21e4:36d4:3::1

;; Query time: 0 msec
;; SERVER: 127.0.0.1#5300(127.0.0.1) (UDP)
;; WHEN: Wed May 08 21:22:33 UTC 2024
;; MSG SIZE  rcvd: 85

With MG_DOCKER_SOLVER_HOST_MACHINE_FALLBACK_ACTIVE: 'false':

# dig plausible.docker @127.0.0.1 -p 5300 aaaa

; <<>> DiG 9.19.18 <<>> plausible.docker @127.0.0.1 -p 5300 aaaa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11546
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;plausible.docker.		IN	AAAA

;; AUTHORITY SECTION:
.			85197	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2024050801 1800 900 604800 86400

;; Query time: 40 msec
;; SERVER: 127.0.0.1#5300(127.0.0.1) (UDP)
;; WHEN: Wed May 08 21:29:32 UTC 2024
;; MSG SIZE  rcvd: 120

@pschiffe commented on GitHub (May 8, 2024): Very nice, seems to work great! Before: ``` # dig plausible.docker @127.0.0.1 -p 5300 aaaa ;; Warning: Client COOKIE mismatch ; <<>> DiG 9.19.18 <<>> plausible.docker @127.0.0.1 -p 5300 aaaa ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7124 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; COOKIE: 068f60a9251b2d84 (bad) ;; QUESTION SECTION: ;plausible.docker. IN AAAA ;; ANSWER SECTION: plausible.docker. 30 IN AAAA fddb:21e4:36d4:3::1 ;; Query time: 0 msec ;; SERVER: 127.0.0.1#5300(127.0.0.1) (UDP) ;; WHEN: Wed May 08 21:22:33 UTC 2024 ;; MSG SIZE rcvd: 85 ``` With `MG_DOCKER_SOLVER_HOST_MACHINE_FALLBACK_ACTIVE: 'false'`: ``` # dig plausible.docker @127.0.0.1 -p 5300 aaaa ; <<>> DiG 9.19.18 <<>> plausible.docker @127.0.0.1 -p 5300 aaaa ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11546 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;plausible.docker. IN AAAA ;; AUTHORITY SECTION: . 85197 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2024050801 1800 900 604800 86400 ;; Query time: 40 msec ;; SERVER: 127.0.0.1#5300(127.0.0.1) (UDP) ;; WHEN: Wed May 08 21:29:32 UTC 2024 ;; MSG SIZE rcvd: 120 ```

kerem referenced this issue

2026-02-26 04:34:48 +03:00

[PR #152] [MERGED] Fixing docker build deprecated option #304