On 2022-04-13 02:42, Stuart Henderson wrote:
On 2022-04-13, J Doe wrote:
For people reading this thread ...
/etc/resolv.conf is the traditional file for configuring the system
resolver(s) while /etc/resolvd.conf is the configuration file for the
resolvd *daemon*, which is also involved in
On 2022-04-13, J Doe wrote:
> For people reading this thread ...
>
> /etc/resolv.conf is the traditional file for configuring the system
> resolver(s) while /etc/resolvd.conf is the configuration file for the
> resolvd *daemon*, which is also involved in the configuration of the
> system
On 2022-03-27 07:05, Stuart Henderson wrote:
On 2022-03-27, Peter J. Philipp wrote:
Some fun facts about DNS. A DNS packet can be 0x hex (or 65535 bytes dec)
maximally. This is true for TCP DNS packets which serve an unsigned short
indicator of length before the packet segment. With UDP
On 2022-03-27, Peter J. Philipp wrote:
> Some fun facts about DNS. A DNS packet can be 0x hex (or 65535 bytes dec)
> maximally. This is true for TCP DNS packets which serve an unsigned short
> indicator of length before the packet segment. With UDP it's a bit different
> a UDP packet can
Hello J Doe/general,
Some comments inline...
On Sat, Mar 26, 2022 at 09:58:01PM -0400, J Doe wrote:
> Hi,
>
> I had a question regarding configuring: /etc/resolvd.conf for use with a
> local caching resolver (using BIND), on the loopback address on OpenBSD 7.0.
>
> This server is a mail server
Hi,
I had a question regarding configuring: /etc/resolvd.conf for use with a
local caching resolver (using BIND), on the loopback address on OpenBSD 7.0.
This server is a mail server and I make use of DNSBL's such as SpamHaus,
which is why I require a local caching resolver.
I see in:
6 matches
Mail list logo
