It seems that this bug is not restricted to Windows. It seems that the test expects a nameserver always to be available.

I guess you can try to apply the patch attached to that RT ticket, whitelist the appropriate network packets in your firewall or just force the installation, ignoring that test failure.

Update: There also is a Windows related bug report. I'm not sure which one applies, but as the rest works OK for you, you should be OK to force the installation.