[GH-ISSUE #139] Fix for slow ping regressed in >= 2.14.0 #56

Closed
opened 2026-02-26 04:33:54 +03:00 by kerem · 5 comments
Owner

Originally created by @russau on GitHub (Jun 3, 2019).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/139

Hello,

Thank you for creating this tool, I'm finding it very useful for some training environments that I create.

I think the fix for #119 has regressed in version 2.14.0. Ping is very fast for me in 2.13.2, but is now slow in version 2.14.0. I have a similar situation to the original ticket: I'm attempting to ping container1 and my /etc/resolv.conf contains a search hsd1.wa.comcast.net.

Let me know if you would like me to provide any more logs or details.

Thanks again!

Originally created by @russau on GitHub (Jun 3, 2019). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/139 Hello, Thank you for creating this tool, I'm finding it very useful for some training environments that I create. I think the fix for #119 has regressed in version 2.14.0. Ping is very fast for me in 2.13.2, but is now slow in version 2.14.0. I have a similar situation to the original ticket: I'm attempting to ping `container1` and my `/etc/resolv.conf` contains a `search hsd1.wa.comcast.net`. Let me know if you would like me to provide any more logs or details. Thanks again!
kerem 2026-02-26 04:33:54 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@mageddo commented on GitHub (Jun 3, 2019):

Do you still have this issue at 2.14.5?

<!-- gh-comment-id:498464215 --> @mageddo commented on GitHub (Jun 3, 2019): Do you still have this issue at 2.14.5?
Author
Owner

@russau commented on GitHub (Jun 3, 2019):

Yes, I was updating some scripts to run the most recent version when I first noticed the problem.

<!-- gh-comment-id:498468501 --> @russau commented on GitHub (Jun 3, 2019): Yes, I was updating some scripts to run the most recent version when I first noticed the problem.
Author
Owner

@mageddo commented on GitHub (Jun 4, 2019):

Okay, I'll try to simulate the issue, I think we really need some automated tests for this

<!-- gh-comment-id:498468893 --> @mageddo commented on GitHub (Jun 4, 2019): Okay, I'll try to simulate the issue, I think we really need some automated tests for this
Author
Owner

@mageddo commented on GitHub (Jun 6, 2019):

Issue was fixed on 2.14.6, can you confirm?

<!-- gh-comment-id:499325850 --> @mageddo commented on GitHub (Jun 6, 2019): Issue was fixed on **2.14.6**, can you confirm?
Author
Owner

@russau commented on GitHub (Jun 9, 2019):

I tested with https://github.com/mageddo/dns-proxy-server/releases/download/2.14.6/dns-proxy-server-linux-amd64-2.14.6.tgz - all looks good!

<!-- gh-comment-id:500188141 --> @russau commented on GitHub (Jun 9, 2019): I tested with https://github.com/mageddo/dns-proxy-server/releases/download/2.14.6/dns-proxy-server-linux-amd64-2.14.6.tgz - all looks good!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dns-proxy-server-mageddo#56
No description provided.