starclick

Tuesday, 23 July 2013

An IPv6 Configuration for Your LAN

Your Subnet as  16-bit subnet:-

IPv4 has the 192.168.*.*, 172.16-31.*, and 10.*.*.* ranges; IPv6 has one range that is enormously bigger than all of those three put together, which can contain

1,329,227,995,784,915,872,903,807,060,280,344,573 devices. The standard is to use a subnet randomly chosen, to minimize conflict. This page has just generated a 16-bit subnet for you, usable for a maximum of 65534 devices:

fd2f:84c9:7052:2627:4a40:71aa:6d88:xxxx
fd2f:84c9:7052:2627:4a40:71aa:6d88::/16 

Using the above 16-bit subnet, the following is the first IP:
fd2f:84c9:7052:2627:4a40:71aa:6d88:0001
and this is the last:
fd2f:84c9:7052:2627:4a40:71aa:6d88:FFFE 

And just as with v4, you will need a subnet mask. The subnet mask for any 16-bit v6 subnet, is:
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:0000 

The reverse DNS zone name, for the above zone, is:
8.8.d.6.a.a.1.7.0.4.a.4.7.2.6.2.2.5.0.7.9.c.4.8.f.2.d.f.ip6.arpa
 
Please note that the GUI of Windows Server 2008 and 2008 R2, support only 64-bit subnets for reverse DNS setup. So to keep subnet size manageably small, we use command line to create the v6 reverse DNS container object, and then add/change using GUI. A command line in Server 2008 and Server 2008 R2, to create the reverse DNS server object for the above v6 subnet, is:

dnscmd . /ZoneAdd 8.8.d.6.a.a.1.7.0.4.a.4.7.2.6.2.2.5.0.7.9.c.4.8.f.2.d.f.ip6.arpa /DsPrimary /DP /domain
The Windows Server GUI works perfectly well for forward DNS of all sizes as well as NIC configuration, and is therefore recommendable.

Your Subnet as  48-bit subnet:-

IPv4 has the 192.168.*.*, 172.16-31.*, and 10.*.*.* ranges; IPv6 has one range that is enormously bigger than all of those three put together, which can contain

1,329,227,995,784,915,872,903,807,060,280,344,573 devices. The standard is to use a subnet randomly chosen, to minimize conflict. This page has just generated a 24-bit subnet for you, usable for a maximum of 16,777,214 devices:

fddd:e112:833d:b6ad:a47b:xxxx:xxxx:xxxx
fddd:e112:833d:b6ad:a47b::/48
 
Using the above 48-bit subnet, the following is the first IP:
fddd:e112:833d:b6ad:a47b:0000:0000:0001

and this is the last:
fddd:e112:833d:b6ad:a47b:FFFF:FFFF:FFFE

And as with v4, you will need a subnet mask. The subnet mask for any 24-bit v6 subnet, is:
FFFF:FFFF:FFFF:FFFF:FFFF:0000:0000:0000
The reverse DNS zone name, for the above zone, is:

b.7.4.a.d.a.6.b.d.3.3.8.2.1.1.e.d.d.d.f.ip6.arpa
Please note that the GUI of Windows Server 2008 and 2008 R2, support only 64-bit subnets for reverse DNS setup. So to keep subnet size manageably small, we use command line to create the v6 reverse DNS container object, and then add/change using GUI. A command line in Server 2008 and Server 2008 R2, to create the reverse DNS server object for the above v6 subnet, is:

dnscmd . /ZoneAdd b.7.4.a.d.a.6.b.d.3.3.8.2.1.1.e.d.d.d.f.ip6.arpa /DsPrimary /DP /domain
The Windows Server GUI works perfectly well for forward DNS of all sizes as well as NIC configuration, and is therefore recommendable.

Your Subnet as  32-bit subnet:-

IPv4 has the 192.168.*.*, 172.16-31.*, and 10.*.*.* ranges; IPv6 has one range that is enormously bigger than all of those three put together, which can contain

1,329,227,995,784,915,872,903,807,060,280,344,573 devices. The standard is to use a subnet randomly chosen, to minimize conflict. This page has just generated a 32-bit subnet for you, usable for a maximum of 4,294,967,293 devices:

fd81:a04f:f070:77ee:61be:f06c:xxxx:xxxx
fd81:a04f:f070:77ee:61be:f06c::/32 

Using the above 32-bit subnet, the following is the first IP:
fd81:a04f:f070:77ee:61be:f06c:0000:0001

and this is the last:
fd81:a04f:f070:77ee:61be:f06c:FFFF:FFFE

And as with v4, you will need a subnet mask. The subnet mask for any 32-bit v6 subnet, is:
FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:0000:0000 

The reverse DNS zone name, for the above zone, is:
c.6.0.f.e.b.1.6.e.e.7.7.0.7.0.f.f.4.0.a.1.8.d.f.ip6.arpa
 
Please note that the GUI of Windows Server 2008 and 2008 R2, support only 64-bit subnets for reverse DNS setup. So to keep subnet size manageably small, we use command line to create the v6 reverse DNS container object, and then add/change using GUI. A command line in Server 2008 and Server 2008 R2, to create the reverse DNS server object for the above v6 subnet, is:

dnscmd . /ZoneAdd c.6.0.f.e.b.1.6.e.e.7.7.0.7.0.f.f.4.0.a.1.8.d.f.ip6.arpa /DsPrimary /DP /domain
The Windows Server GUI works perfectly well for forward DNS of all sizes as well as NIC configuration, and is therefore recommendable.

Your Subnet as  64-bit subnet:-

IPv4 has the 192.168.*.*, 172.16-31.*, and 10.*.*.* ranges; IPv6 has one range that is enormously bigger than all of those three put together, which can contain

1,329,227,995,784,915,872,903,807,060,280,344,573 devices. The standard is to use a subnet randomly chosen, to minimize conflict. This page has just generated a 64-bit subnet for you, usable for a maximum of 18,446,744,073,709,551,613 devices:

fd8e:c733:f055:134e:xxxx:xxxx:xxxx:xxxx
fd8e:c733:f055:134e::/64

Using the above 64-bit subnet, the following is the first IP:
fd8e:c733:f055:134e:0000:0000:0000:0001

and this is the last:
fd8e:c733:f055:134e:FFFF:FFFF:FFFF:FFFE 

And as with v4, you will need a subnet mask. The subnet mask for any 64-bit v6 subnet, is:
FFFF:FFFF:FFFF:FFFF:0000:0000:0000:0000
The reverse DNS zone name, for the above zone, is:

e.4.3.1.5.5.0.f.3.3.7.c.e.8.d.f.ip6.arpa
64-bit subnets are certainly usable on a LAN, but they are far larger than necessary, and smaller ones may be more manageable; please see the links below! Please note that Windows Server 2008 and 2008 R2 support only 64-bit subnets (the kind on this page) in the GUI reverse DNS setup.

If you would like to create a reverse DNS zone for the above subnet by command line in Windows Server 2008 (or 2008 R2), the following works well:
dnscmd . /ZoneAdd e.4.3.1.5.5.0.f.3.3.7.c.e.8.d.f.ip6.arpa /DsPrimary /DP /domain

No comments:

Post a Comment

Every Admin Should Know These Commands Active Directory 1.   To quickly list all the groups in your domain, with members, run this c...