public inbox for gwml@vger.gnuweeb.org
 help / color / mirror / Atom feed
From: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: Ahmad Gani <reyuki@gnuweeb.org>,
	"GNU/Weeb Mailing List" <gwml@vger.gnuweeb.org>
Subject: Re: [PATCH gwproxy v13 0/8] Initial work on integration of DNS parser lib in gwproxy
Date: Thu, 2 Oct 2025 15:19:30 +0700	[thread overview]
Message-ID: <CAOG64qPuT-iTsvg9wLB9JnM3CKGa7Q-a8h8Qom_rt_X1BCXg5Q@mail.gmail.com> (raw)
In-Reply-To: <20251002080747.GB18177-ammarfaizi2@gnuweeb.org>

On Thu, Oct 2, 2025 at 3:07 PM Ammar Faizi wrote:
> Anyway, I don't see the DNS cache integration here. Please integrate it
> in the next revision. I think when we use the raw DNS resolver, we no
> longer need this option to control the DNS cache:
>
>   -L, --socks5-dns-cache-secs=sec SOCKS5 DNS cache duration in seconds (default: 0)
>
> Instead, the cache duration can be taken from the TTL retrivied from
> the DNS server. That's one of the advantages of creating our own DNS
> resolver. I introduced the -L option because getaddrinfo() doesn't
> expose the TTL to the caller.
>
> For the initial experimental stage, you can write a rejection rule at
> initalization. If the raw DNS feature is used and the -L option is
> specified, reject it, show an error message that says -L option is
> not supported with the raw DNS feature.

Ok, I'll do that

  reply	other threads:[~2025-10-02  8:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30  8:54 [PATCH gwproxy v13 0/8] Initial work on integration of DNS parser lib in gwproxy Alviro Iskandar Setiawan
2025-09-30  8:54 ` [PATCH gwproxy v13 1/8] gwproxy: Remove 'struct gwp_dns_query' declaration Alviro Iskandar Setiawan
2025-09-30  8:54 ` [PATCH gwproxy v13 2/8] gwproxy: Introduce __unused macro Alviro Iskandar Setiawan
2025-09-30  8:54 ` [PATCH gwproxy v13 3/8] Add DNS parser code Alviro Iskandar Setiawan
2025-09-30  8:54 ` [PATCH gwproxy v13 4/8] Add DNS resolver code Alviro Iskandar Setiawan
2025-09-30  8:54 ` [PATCH gwproxy v13 5/8] dns_resolver: Add DNS resolution interface APIs Alviro Iskandar Setiawan
2025-09-30  8:54 ` [PATCH gwproxy v13 6/8] gwproxy: Introduce --dns-server and --raw-dns Alviro Iskandar Setiawan
2025-09-30  8:54 ` [PATCH gwproxy v13 7/8] epoll: Intregrate the raw DNS feature to epoll Alviro Iskandar Setiawan
2025-09-30  8:54 ` [PATCH gwproxy v13 8/8] Makefile: Introduce --use-new-dns-resolver configure option Alviro Iskandar Setiawan
2025-10-02  7:05 ` [PATCH gwproxy v13 0/8] Initial work on integration of DNS parser lib in gwproxy Ammar Faizi
2025-10-02  7:20   ` Alviro Iskandar Setiawan
2025-10-02  8:07     ` Ammar Faizi
2025-10-02  8:19       ` Alviro Iskandar Setiawan [this message]
2025-10-26 21:10         ` Ammar Faizi
2025-10-29 16:33           ` Alviro Iskandar Setiawan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOG64qPuT-iTsvg9wLB9JnM3CKGa7Q-a8h8Qom_rt_X1BCXg5Q@mail.gmail.com \
    --to=alviro.iskandar@gnuweeb.org \
    --cc=ammarfaizi2@gnuweeb.org \
    --cc=gwml@vger.gnuweeb.org \
    --cc=reyuki@gnuweeb.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox