i do not love the
https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-alt-tld-10 draft,
but i would love even less to see it reinvented in our ignorance.
re:
Ted Lemon wrote:
It would probably be easier to get internal.arpa, similar to home.arpa.
You could use home.arpa now, but it would look a little funny... :)
On Tue, Jul 24, 2018 at 10:52 AM, A. Schulze <s...@andreasschulze.de
<mailto:s...@andreasschulze.de>> wrote:
Hello,
some times ago there was an proposal (?) from Warren Kumari to
define a zone "internal." for internal use.
We consider a major DNS redesign of a large enterprise network. Part
of the network is private (RFC1918 address space in use)
some other parts are public. The whole network is currently
organized as subdomains of example.com <http://example.com>.
One problem is the inability of users to distinguish the
public/private state of different subdomains.
sub1.example.com <http://sub1.example.com> is public,
sub2.example.com <http://sub2.example.com> isn't :-/
For that I like the proposal to use "internal." But that's far away
from being a standard.
So I like to ask about alternatives...
Thanks for suggestions
Andreas
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org <mailto:DNSOP@ietf.org>
https://www.ietf.org/mailman/listinfo/dnsop
<https://www.ietf.org/mailman/listinfo/dnsop>
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
--
P Vixie
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
