One DNS unit test failing about nhin-d HOT 8 CLOSED

To run, the "test" actually goes out onto the public Internet and requires that:
1. Your firewalls (Local & Corporate) allows TCP traffic on port 53. 
2. The hsgincubator test BIND deployment that hosts the CERTS is up and 
running. Or you alter the test to call an alternative BIND host. I typically 
run the test against one I run locally. 

The test should therefore only be run on demand... and was not part of the 
default unit tests runs. 

We still haven't figured out how (and where) to test this - open problem and 
solutions are welcome. The unit test exists so that at least the developer who 
changes the code can run some default test code...

Arien - could you check your ports etc, as noted in the comment above. Thanks. 

No port issue. The problem is transient, and happens on random DNS lookups -- 
it's not specific to one test. I'd suspect it was timeout, but the tests 
execute in 5 seconds, and the timeout is 10 seconds (10000).

Based on the stack trace (see below), the problem is in ValidateRequestID, but 
the stack trace isn't more informative than that.

-----
Here's the stack trace:

DnsResolverTests.BasicResolverTests.ResolveCert("nhin.whinit.org.hsgincubator.co
m") [FAIL]
   DnsResolver.DnsProtocolException : Exception of type 'DnsResolver.DnsProtocolException' was thrown.
   Stack Trace:
      c:\source\nhin-d\csharp\dns\DnsClient.cs(774,0): at DnsResolver.DnsClient.ExecuteTCP()
      c:\source\nhin-d\csharp\dns\DnsClient.cs(346,0): at DnsResolver.DnsClient.Resolve(DnsRequest request)
      c:\source\nhin-d\csharp\dns\DnsClient.cs(454,0): at DnsResolver.DnsClient.ResolveCERT(String domain)
      c:\source\nhin-d\csharp\dns\DnsClient.cs(498,0): at DnsResolver.DnsClient.ResolveCERTFromNameServer(String domain,
 IPAddress nameserver)
      c:\source\nhin-d\csharp\dns\DnsClient.cs(486,0): at DnsResolver.DnsClient.ResolveCERTFromNameServer(String domain)

      c:\source\nhin-d\csharp\unittests\dns\BasicResolverTests.cs(69,0): at DnsResolverTests.BasicResolverTests.ResolveC
ert(String domain)

Cool. That helps!

I'll try to investigate this by Monday. Can't promise though - too much to get 
done. 

This should be fixed now (hopefully). 
- Cleaned up the request ID and other handling
- Tested against several public DNS servers

Tests will continue to fail for some internal firewalls, which block TCP Port 
53. There, you will get a "connection refused" type of error. 

Please bounce this back if you continue to see issues.