AD DS: DNS Server requires static IPv4 and IPv6 IP Addresses


While installing and configuring Server 2008 (Standard), I decided to set up the AD DS service.
AD DS requires that the DNS service be set up as well.  DNS doesn’t function properly if you’re getting a DHCP address.

I personally haven’t yet made time to to educate myself about IPv6, though I should.  The DNS setup process will complain if you do not have a static IPv6 address configured.

My server has two NICs.  Their IPv4 addresses are 192.168.3.2 and 192.168.3.3, respectively.
I went to the following website – http://www.subnetonline.com/pages/subnet-calculators/ipv4-to-ipv6-converter.php, plugged in the respective IPv4 addresses, and used the tool to pull out the equivalent IPv6 address, subnet mask, and default gateway.

I then also set the primary DNS server to 127.0.0.1 (in IPv6 notation of course, which I believe is 0:0:0:0:0:0:7f00:1),
and my local router – 192.168.3.1, again in IPv6 notation.

Originally posted 2009-07-02 09:00:17.

Other articles:

, , , , , , , , ,

  1. #1 by Lawrence Hughes on July 2, 2009 - 7:05 pm

    You definitely HAVEN’T taken the time to come up to speed on IPv6.

    1. IPv6 loopback address is ::1, not ::7f00:1.

    2. You should not be using IPv4 compatible addresses. You need to determine what 64 bit prefix your network is using (determined by ISP, either direct or tunneled). Say it is 2001:12:34:56::/64. I use hard coded addresses for my AD DNS servers as follows: 1Pv4: 172.20.0.11 and 172.20.0.12. For consistency, I used hard coded addresses (assuming above bogus prefix) of 2001:12:34:56::0b and 2001:12:34:45::0c (the low 64 bits being the same as the low 8 bits in IPv4). There is no reason they must be simlar.

    3. Unless your router supports IPv6 (unlikely, unless you have one of the new D-Link units, or have bought a Cisco or Juniper router that does, or have rolled your own with Linux or FreeBSD), your router has no IPv6 address (and no Router Advertisement daemon, which supplies the prefix for your network stateless autoconfig). You should get an IPv6 aware router/firewall and configure it. I recommend one that supports 6in4 tunneling, then sign up for tunneled IPv6 service from some handy virtual ISP (Hurricane Electric, go6, etc).

    4. If you have no RAD running, stateless autoconfig won’t work, so you need to specify hard coded IPv6 addresses for ALL machines, not just your AD machines. If you have any XP machines, you may find SolidIPConfig useful, which you can download at http://www.infoweapons.com for free.

    • #2 by Harv on July 3, 2009 - 2:16 pm

      Lawrence,

      thanks for the useful feedback. I really haven’t had a chance to look into IPv6 at all. Once I get some time I will do a short piece for those who are still confused. Glad you stopped by!

(will not be published)

Bad Behavior has blocked 201 access attempts in the last 7 days.

© 2008-2010 Learn With Harv: Blog All Rights Reserved -- Copyright notice by Blog Copyright

Learn With Harv: Blog is Digg proof thanks to caching by WP Super Cache