First of all, don't use .loc as an internal TLD. There are *many*
proposals in process with ICANN for establishing new TLDs, and for all
you know, .loc might be one of them. If .loc gets established on the
Internet, and you're using it internally, that presents abundant
opportunities for confusion and failure.
Use a publically-registered domain, a descendant of a
publically-registered domain, or potentially, one of the reserved TLDs
in RFC 6761.
I'm not sure what your question is, exactly. Set up the root zone, slave
it, publish 2 or more of the master/slaves in the NS records, delegate
whatever TLD you're going to use, set up *that* zone, lather, rinse,
repeat, for the entire hierarchy. Anyone who reads _DNS_and_BIND_ should
be able to set up an internal-root infrastructure, IMO (although, sadly,
the later editions don't seem as aligned to internal-root as they used
to be).
- Kevin
On 3/12/2014 11:07 AM, Peter wrote:
Hi guys,
I'm doing a virtual internet (internal net) for several VPS's. My goal
is to simulate the Internet root servers and the ISP:s domain servers,
which are hosting the actual domains. I want to the create several DNS
nameservers that will contain the specific domain under the "xxx.loc,
yyy.loc, zzz.loc".
1 server for the .loc root
3 servers for xxx.loc (server1), yyy.loc (server2), zzz.loc (server3)
Running BIND 9 at every server.
Any suggestions or good links are highly appreciated.
Best regards,
Peter
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to
unsubscribe from this list
bind-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/bind-users
