It is a very simple request->response based interface, only having one
query at a time per dnsserver process..
Anything received which is a IP address is assumed to be a request for a
reverse lookup from IP, else it is assumed to be a forward lookup based
on the hostname. Result is one of
The lookup failed
"$fail <a descriptive error message>"
Result of a reverse lookup
"$name <ttl> <hostname>"
Result of a normal lookup
"$addr <ttl> <ip1> <ip2>..."
There is also a couple of magic "commands"
$hello, results in $alive being returned
$shutdown, tells the helper to exit cleanly
As you can see the protocol does only support one query at a time, so
replacing dnsserver by a multithreaded one won't do much good as Squid
can only send one query at a time to each helper..
The internal DNS client does not share these limitations in concurrency,
and can manage a "unlimited" amount of concurrent DNS lookups.
Regards
Henrik
Jigar Rasalawala wrote:
>
> Hi, guys
>
> I am running Squid 2.4.STABLE4 on RedHat 7.1. I compiled my squid with
> --disable-internal-dns option.
> I want to use my own multi-threaded DNS server program instaed of
> DNSSERVER helper.
>
> How can I find documentation about interface the way squid and DNSSERVER
> talks to each other ??
>
> Any help or suggestion appriciated..
>
> Thanks
> Jigar
Received on Tue Sep 10 2002 - 16:36:39 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:10:11 MST