starred/dns-proxy-server-mageddo

Fork 0

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

[GH-ISSUE #576] Working successfully but also provide some errors #189

New issue

Closed

opened 2026-02-26 04:34:19 +03:00 by kerem · 7 comments

kerem commented

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

Owner

Originally created by @horlarme on GitHub (Sep 20, 2024).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/576

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.

Originally created by @horlarme on GitHub (Sep 20, 2024). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/576 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.

kerem

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

closed this issue
added the
discussion
label

kerem commented

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

Author

Owner

@horlarme commented on GitHub (Sep 20, 2024):

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 commented on GitHub (Sep 20, 2024): 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 ````

kerem commented

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

Author

Owner

@horlarme commented on GitHub (Sep 20, 2024):

@horlarme commented on GitHub (Sep 20, 2024): Found similar issue https://github.com/mageddo/dns-proxy-server/issues/68

kerem commented

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

Author

Owner

@mageddo commented on GitHub (Sep 20, 2024):

Hey, Which version are you using @horlarme ?

@mageddo commented on GitHub (Sep 20, 2024): Hey, Which version are you using @horlarme ?

kerem commented

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

Author

Owner

@horlarme commented on GitHub (Sep 20, 2024):

Hey, Which version are you using @horlarme ?

3.25.10-snapshot

@horlarme commented on GitHub (Sep 20, 2024): > Hey, Which version are you using @horlarme ? 3.25.10-snapshot

kerem commented

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

Author

Owner

@horlarme commented on GitHub (Sep 20, 2024):

Update.

If the IP address to the container is manually set (as seen in the screenshot below), the issue will be resolved but then it defeats the reason for using the service.

@horlarme commented on GitHub (Sep 20, 2024): Update. If the IP address to the container is manually set (as seen in the screenshot below), the issue will be resolved but then it defeats the reason for using the service. <img width="935" alt="image" src="https://github.com/user-attachments/assets/f1cba88a-2954-4103-83bd-af546e7d9a31"> <img width="342" alt="image" src="https://github.com/user-attachments/assets/f4cfb61b-e8ba-44b9-b51b-b8b502b4324e">

kerem commented

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

Author

Owner

@horlarme commented on GitHub (Sep 20, 2024):

@mageddo any suggestions on what I might be doing wrong?

@horlarme commented on GitHub (Sep 20, 2024): @mageddo any suggestions on what I might be doing wrong?

kerem commented

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

Author

Owner

@horlarme commented on GitHub (Sep 21, 2024):

Update.
I have decided to use caddy as a container on the same networks as my container. This currently allows me to use the hostnames without the service.

Thank you for your time.

@horlarme commented on GitHub (Sep 21, 2024): Update. I have decided to use caddy as a container on the same networks as my container. This currently allows me to use the hostnames without the service. Thank you for your time.

kerem referenced this issue

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

[PR #189] [MERGED] Support for absolute paths on config files (#188) #328