> On 15 May 2024, at 04:34, John Thurston wrote:
>
> There are several 'special-use' domain names I'm pondering
> • invalid.
> • test.
> • onion.
> My read of the RFCs indicate they should result in NXDOMAIN, and not be
> passed for resolution.
> RFC 6761 (test. Section 6.2.4 /
On Tue, May 14, 2024 at 2:34 PM John Thurston wrote:
>
> There are several 'special-use' domain names I'm pondering
>
> invalid.
> test.
> onion.
>
> My read of the RFCs indicate they should result in NXDOMAIN, and not be
> passed for resolution.
>
> RFC 6761 (test. Section 6.2.4 / invalid.
There are several 'special-use' domain names I'm pondering
* invalid.
* test.
* onion.
My read of the RFCs indicate they should result in NXDOMAIN, and not be
passed for resolution.
RFC 6761 (test. Section 6.2.4 / invalid. Section 6.4.4)
caching DNS servers SHOULD, by default, generate
A part of the subdomains are managed by us, others subdomains by an other
entity.
So we can't configure a generic target for all subdomains as each entity has
its own target for SRV entries.
-Message d'origine-
De : bind-users De la part de Matus UHLAR -
fantomas
Envoyé : mardi 14 mai
Le 14/05/2024 à 15:08, DEMBLANS Mathieu a écrit :
Hello,
I have a question about configuration simplification for SRV
configuration (maybe it can be applyed for other entries).
We manage multiple subdomain of a main one (server1.example.com,
server2.example.com,…).
For A and MX entries,
On 14.05.24 13:08, DEMBLANS Mathieu wrote:
I have a question about configuration simplification for SRV configuration
(maybe it can be applyed for other entries).
We manage multiple subdomain of a main one (server1.example.com,
server2.example.com,...).
For A and MX entries, we use a general
Hello,
I have a question about configuration simplification for SRV configuration
(maybe it can be applyed for other entries).
We manage multiple subdomain of a main one (server1.example.com,
server2.example.com,...).
For A and MX entries, we use a general domain definitions with wildcard but
7 matches
Mail list logo