Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've set up a test domain to experiment with windows server 2012.

Initially I kept my test machines on a isolated network, but today I installed a pfsense machine to route some traffic to the internet.

Upon establishing the internet connection I realized that recursive DNS lookups did not work in my brand new domain, even though 'Use root hints if no forwarders are available' was checked and I could use nslookup to connect to (one of) the root hints.

I tried adding google's resolvers ( and as forwarders and that got DNS working for non-local records.

I removed the forwarders to google. I then removed the three default forwarders (fec0:0:0:ffff::1, fec0:0:0:ffff::2, fec0:0:0:ffff::3) and the server was able to use the root hints properly.

My router/internet access is only ipv4, so the only ipv6 traffic I'd expect is domain local.

Is it supposed to be necessary to remove the ipv6 forwarders for the server to do recursive lookups, or is there some configuration I am missing?

share|improve this question
Default forwarders? This is new to me.. are you sure that nobody else added them? – pauska May 22 '13 at 8:42
I'm sure. I'm the only one with access to the machines. – azzid May 22 '13 at 9:13
up vote 2 down vote accepted

Ouch! Use of the fec0::/10 IPv6 address block (which used to be the site-local addresses) has been deprecated in September 2004. Those addresses should never be used anymore, and certainly not as a default.

This is a bug in Windows Server 2012. Yes, you should definitely remove them.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.