An unknown error occurred while validating the server dns

Following the recipe for v1.0.0.0 from MS finally made it work for me: Microsoft Visual Studio Installer Projects Unfortunately we couldn't address all cases of the command line issue for this release as we're still investigating the appropriate way to address them.What we do have is a workaround that we believe will work for almost all of them.I'm migrating one of my clients from Windows Server 2003 to 2008.However, DNS recursive query and nslookup are failing on the new 2008 DC.Can you mimic the 2003 server's rules in the firewall for the 2008's server's IP?As a test, unplug the 2003 server, then change the 2008 server's IP to the one the 2003 server is using, then test it. (of course do this after hours, especially if the 2003 server is a prod server).If you are still suffering this issue then you can try to change the DWORD value for the following registry value to 0: That error didn't stop me from deploying, building, debugging (or anyting) my project it just annoyed me.

It sounds like the query is not passing through or returning through a firewall. All outbound LAN traffic is allowed except port 25 from non-mail servers.

In the meantime, I'm using Open DNS & some Time Warner DNS snagged from another local Time Warner client because all the other DNS servers I could find on the worthless Time Warner business-class "support" website fail, too. I would have suggested to try 4.2.2.2, but it didn't occur to me it would be an external DNS issue.

I can't really pin point any changes that would have affected this short of windows updates.

Pretty worthless, but maybe you can glean something from the results that I missed: ================================================== Server: xxx.Address: ------------ Got answer: HEADER: opcode = QUERY, id = 78, rcode = NXDOMAIN header flags: response, auth. questions = 1, answers = 0, authority records = 1, additional = 0 QUESTIONS: xxxxxx.com, type = A, class = IN AUTHORITY RECORDS: - ttl = 3600 (1 hour) primary name server = xxx.responsible mail addr = hostmaster serial = 10377 refresh = 900 (15 mins) retry = 600 (10 mins) expire = 86400 (1 day) default TTL = 3600 (1 hour) ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 79, rcode = NXDOMAIN header flags: response, auth. questions = 1, answers = 0, authority records = 1, additional = 0 QUESTIONS: xxxxxx.com, type = AAAA, class = IN AUTHORITY RECORDS: - ttl = 3600 (1 hour) primary name server = xxx.responsible mail addr = hostmaster serial = 10377 refresh = 900 (15 mins) retry = 600 (10 mins) expire = 86400 (1 day) default TTL = 3600 (1 hour) ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 80, rcode = SERVFAIL header flags: response, want recursion, recursion avail. Ace My suspicions were port 53 blocked, too, because if I add the old 2003 server to the 2008's forwarders, it works.

questions = 1, answers = 0, authority records = 0, additional = 0 QUESTIONS: microsoft.com, type = A, class = IN ------------ ------------ Got answer: HEADER: opcode = QUERY, id = 81, rcode = SERVFAIL header flags: response, want recursion, recursion avail. However, I can't find where (or even if) its blocked.

Search for an unknown error occurred while validating the server dns:

an unknown error occurred while validating the server dns-70an unknown error occurred while validating the server dns-37an unknown error occurred while validating the server dns-57an unknown error occurred while validating the server dns-33

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “an unknown error occurred while validating the server dns”