Working successfully but also provide some errors

[horlarme]

Good day,

I successfully installed and configured the DNS server using docker but when I do a lookup of any of the docker endpoints, I get an answer but at same time an error

> nslookup dns.mageddo
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   dns.mageddo
Address: 172.17.0.4
;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out
;; no servers could be reached

> nslookup dns.mageddo
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   dns.mageddo
Address: 172.17.0.4
** server can't find dns.mageddo: NXDOMAIN

> nslookup dns.mageddo
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   dns.mageddo
Address: 172.17.0.4
;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out
** server can't find dns.mageddo: NXDOMAIN

> nslookup google.com
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   google.com
Address: 142.251.33.78
Name:   google.com
Address: 2607:f8b0:400a:806::200e

> nslookup test.api.plap.xyz
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   test.api.plap.xyz
Address: 5.78.119.248

> nslookup host.docker
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   host.docker
Address: 172.21.0.1

> nslookup dns.mageddo
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   dns.mageddo
Address: 172.17.0.4
;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out
** server can't find dns.mageddo: NXDOMAIN

From the above, you'll notice the host.docker, google.com and test.api.plap.xyz worked without any other response but dns.mageddo worked but at same time provides error. Is this something I should be concerned about?

Thank you.

[horlarme]

I think it actually is an issue for me as it takes 11 seconds (sometimes) to resolve the hostname to my container

 ~  curl -I backend-staging.docker:8080 6 х  with user@api  at 09:01:36 AM 
HTTP/1.1 200 OK
Server: nginx
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
X-Powered-By: PHP/8.2.21
Cache-Control: no-cache, private
Date: Fri, 20 Sep 2024 09:01:56 GMT
Max-Age=7200; path=/; httponly; samesite=lax
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer-when-downgrade
Strict-Transport-Security: max-age=31536000; includeSubDomains

 ~  curl -I backend-staging.docker:8080 ✔  took 11s  with user@api  at 09:01:56 AM 
HTTP/1.1 200 OK
Server: nginx
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
X-Powered-By: PHP/8.2.21
Cache-Control: no-cache, private
Date: Fri, 20 Sep 2024 09:02:04 GMT
Max-Age=7200; path=/; httponly; samesite=lax
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer-when-downgrade
Strict-Transport-Security: max-age=31536000; includeSubDomains

 ~ ✔ │ with user@api  at 09:02:04 AM 

[horlarme]

Found similar issue https://github.com/mageddo/dns-proxy-server/issues/68

[mageddo]

Hey, Which version are you using @horlarme ?

[horlarme]

Hey, Which version are you using @horlarme ?

3.25.10-snapshot