Hello Carsten and Kevin
Thanks for your answers. As a short summary, I will use (and recommend) the
following ways:
- consider .local/.loc/.intra/.lan etc. as legacy which should be eliminated
(Microsoft officially supports Active Directory domain renaming procedures
for that).
- preferred
On 5/26/2013 2:36 PM, Andreas Meile wrote:
Hello BIND users
The following post discusses some complexer questions in context with
enabling dual-stack in corporate networks. It's very TCP/IP generic
but has also a lot to do with DNS (and of course BIND which I use to
implement it = all
Hello Andreas,
Andreas Meile mailingli...@andreas-meile.ch writes:
First question for discussion: Is it recommended to replace example.local
into intra.example.com for example because it's now possible to restore
the public DNS hierarchy? See the following:
In my view, using a namespace
Hello BIND users
The following post discusses some complexer questions in context with
enabling dual-stack in corporate networks. It's very TCP/IP generic but has
also a lot to do with DNS (and of course BIND which I use to implement it =
all examples are in BIND syntax) so I hope it's not too
4 matches
Mail list logo
