Overblog Suivre ce blog
Editer l'article Administration Créer mon blog
18 juillet 2013 4 18 /07 /juillet /2013 15:11

We'll see in this post using GUA ( Global Unicast Addresses ) for our DNS Server and what it involves compared to ULA.
See previous post about the basics of DNS Server, using ULA.




As stated during the two previous posts, our DNS Server will only be authoritative upon our local network. We'll leave our public servers DNS management at the registrar level. See the two previous posts for explainations and details.

[G] represents our /48 GUA prefix throughout this post ( 2001:0DB8:0::/48 as an example )


Subnet design of the GUA network


As we're using GUA ( Global Unicast Addresses ), we need to use a clear separation between our authority and our non-authority zones. We'll use subnets for this :




the [G]:2::/64 and [G]:1::/64 subnets will be for our non-public network
the [G]:0::/64 will be for our public-access network

for this, we create two reverse-lookup zones :

new reverse lookup zone :

    Primary zone




    do not allow dynamic updates

new reverse lookup zone :

    Primary zone




    do not allow dynamic updates

we then add the AAAA records for our network nodes :

add AAAA records for PC1, PC2, vefsna, router1, Router2

Using both ULA and GUA on the non-public network

of course, we can register both the ULA and GUA non-public subnets. We just have to register both the ULA and GUA reverse-lookup zones, and both ULA and GUA AAAA records for the nodes.

the only point to choose is wether to register distinct hosts and routers  names for ULA and GUA.
[G] being our /48 GUA prefix and [H] being our /48 ULA prefix, we could have :

[G]:3::210    PC1
[H]:3::210    PC1


[G]:3::210    PC1gua
[H]:3::210    PC1

it is just a design choice.


Partager cet article

Repost 0
Published by computer outlines - dans Windows Server 2008 R2
commenter cet article



  • : Computer Outlines Blog
  • : Blog mainly focused over IPv6, Windows Server, and Networking in general.
  • Contact