Hi,
On Mon, 5 Dec 2022, Matthijs Mekking wrote:
'parental-agents' work the same as 'primaries'. It only supports addresses.
Listing them as domain names would technically be possible to implement, but
it requires an authoritative server to act as an resolver. Adding resolver
code to the
On 05-Dec-22 11:17, vom513 wrote:
On Dec 5, 2022, at 4:06 AM, Matthijs Mekking wrote:
'parental-agents' work the same as 'primaries'. It only supports addresses.
Listing them as domain names would technically be possible to implement, but it
requires an authoritative server to act as an
Hello Petr:
On 12/5/22 4:35 AM, Petr Špaček wrote:
> On 05. 12. 22 3:49, Fred Morris wrote:
>> If the UDP query returns TC=1 DiG retries with TCP. I want to see the
>> UDP results and am unable to. Specifying +notcp makes no difference.
>> The correct option is +ignore:
>>
>> # dig
> On Dec 5, 2022, at 4:06 AM, Matthijs Mekking wrote:
>
> 'parental-agents' work the same as 'primaries'. It only supports addresses.
>
> Listing them as domain names would technically be possible to implement, but
> it requires an authoritative server to act as an resolver. Adding resolver
On 05. 12. 22 3:49, Fred Morris wrote:
If the UDP query returns TC=1 DiG retries with TCP. I want to see the
UDP results and am unable to. Specifying +notcp makes no difference. The
correct option is +ignore:
# dig @127.0.0.1 'web_client\;*\;athena\;*.keys.redis.sophia.m3047' txt
+notcp
On 04-Dec-22 21:34, vom513 wrote:
Hello all,
So I set up parental-agents lists for my zones, and actually got to see it work
(awesome !). bind detected the parent DS records and acted accordingly.
However, I currently have these lists configured using the IP (v4 only at the
moment)
'parental-agents' work the same as 'primaries'. It only supports addresses.
Listing them as domain names would technically be possible to implement,
but it requires an authoritative server to act as an resolver. Adding
resolver code to the path of an authoritative server is like crossing
the
7 matches
Mail list logo
