Windows 7 and Prefer IPV4 DNS
I have a small network with Server 2012 Standard and a handful of Windows 7 and 8.1 devices. The server handles DHCP and DNS for IPV4. Now my ISP has started offering IPV6 as well so I've thrown that into the mix and it's not playing nice. I don't have a static IP or even an assigned range for IPV6, addresses are assigned using stateless autoconfiguration. That means I can't setup a IPV6 scope or DNS server on my local server, the IP's are assigned rather by my ISP.
My solution to this was to change the registry setting to make Windows prefer IPV4. This works fine on Windows 8.1. Unless I go to a site where IPV6 is needed IPV6 does not come into play. However Windows 7 is another story, I can ping an address and it will return the IPV4 address after making the change. BUT it uses the IPV6 DNS servers as the primary DNS servers. This is a big problem because they are my ISP's name servers which can't resolve my local domain! The IPV4 name servers are third and fourth on the list and they never seem to get checked, so logging into the domain fails.
I've tried changing the prefix priorities to no avail. There just does not seem to be any way to force Windows 7 to prefer the IPV4 DNS servers that I can find.
Any suggestions besides turning off IPV6?
My solution to this was to change the registry setting to make Windows prefer IPV4. This works fine on Windows 8.1. Unless I go to a site where IPV6 is needed IPV6 does not come into play. However Windows 7 is another story, I can ping an address and it will return the IPV4 address after making the change. BUT it uses the IPV6 DNS servers as the primary DNS servers. This is a big problem because they are my ISP's name servers which can't resolve my local domain! The IPV4 name servers are third and fourth on the list and they never seem to get checked, so logging into the domain fails.
I've tried changing the prefix priorities to no avail. There just does not seem to be any way to force Windows 7 to prefer the IPV4 DNS servers that I can find.
Any suggestions besides turning off IPV6?
ASKER
Yes, I used the FixIt in that article which creates an entry "DisabledComponents=0x20" in the IPV6 parameters. This does in fact result in an IPV4 address being returned as expected. It does NOT result in the IPV4 DNS servers being prefered however.
If I do an ipconfig /all my DNS servers would be listed as something like...
2600::1
2600::2
192.168.1.2
192.168.1.3
If I type nslookup it would show my current nameserver as 2600::1. Which is external and not capable of resolving my domain.
So to make this more clear.
Ping www.google.com ... gets me 74.125.225.212
Ping mydomain.local ... gets me could not find host
Hope that makes sense.
If I do an ipconfig /all my DNS servers would be listed as something like...
2600::1
2600::2
192.168.1.2
192.168.1.3
If I type nslookup it would show my current nameserver as 2600::1. Which is external and not capable of resolving my domain.
So to make this more clear.
Ping www.google.com ... gets me 74.125.225.212
Ping mydomain.local ... gets me could not find host
Hope that makes sense.
Just because your ISP is offering it doesn't mean you have to use it.
Even if the ISP is giving IPv6 addressing to you that shouldn't have any effect whatsoever on your internal IPv4 configuration.
Even if the ISP is giving IPv6 addressing to you that shouldn't have any effect whatsoever on your internal IPv4 configuration.
ASKER
That's true, and this is purely an experimental setup and I don't have any practical reason that I need IPV6. It's just personal satisfaction of getting both IPV4 and IPV6 playing nice together. It seems though unless you are an enterprise with a designated block of IPV6 addresses, it's not very practical to use in a client-server environment. Because as it currently stands there is no NAT in the IPV6 world, there's no other way to allow servers to have a static IP.
Well, there's unique local addressing but that's very limiting since devices with ULA's can communicate with the public internet.
Oh, and IPV6 should not have an effect on the IPV4 network, but it DOES. I give up, this appears to be an exercise in futility. Thank you to those who tried to help.
Well, there's unique local addressing but that's very limiting since devices with ULA's can communicate with the public internet.
Oh, and IPV6 should not have an effect on the IPV4 network, but it DOES. I give up, this appears to be an exercise in futility. Thank you to those who tried to help.
We have been avoiding the problem by staring to implement routers that can block IPv6 traffic to/from the public side. One concern is a device getting an IPv6 DHCP address from an unknown source such as a neighbor with malicious intent.
IPv6 doesn't interfere with IPv4. You need to tell your devices to prefer IPv4 that's all. The two are designed to be able to run together, and they do just that.
As ISP's are implementing IPv6, there are some issues arising such as rouge IPv6 DHCP servers, and Exchange will send e-mail using IPv6 and sites such as GMail will bounce the mail unless IPv6 PTR records are in place. To do that you have to implement IPv6 public DNS, configure the server, and more, such that blocking it at the router in some cases is easier for now. It's not a long term solution.
Internally they live happily together and are implemented and managed by default with Windows servers.
Internally they live happily together and are implemented and managed by default with Windows servers.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Is not blocking at the router what I had suggested?
ASKER
Required resources outside of this board to find final solution. It's still kind of a kludge, but that just seems to be the state of IPv6 currently.
Link Here: http://support.microsoft.com/kb/929852
This way you can have which one you want.