An unknown error occurred while validating the server dns Answer dating love marriage meaning question real real sex

Frankly, now I'm not sure how 2003 server was working at all since these are the only external DNS listed anywhere in it. I bet if you ran nslookup with the d2 switch (set d2), that you will find at the recursion request portion, it would say recursion is not available.

an unknown error occurred while validating the server dns-31

questions = 1, answers = 0, authority records = 0, additional = 0 QUESTIONS: microsoft.com, type = AAAA, class = IN ------------ *** xxx.can't find microsoft.com: Server failed ================================================== The Servfail is saying that it could not get the response from the server it was using, and NXDDOMAIN is saying the domain doesn't exist. Firewall is pf Sense (Free BSD-based packet filter).

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.

However, as I said before I added firewall rules and disabled firewalls, I can telnet port 53 from this server to the external DNS but nslookup with set vc still fails. The startup looks like this: C:\nslookup Default Server: Un Known Address: ::1 Colons made me suspicious of IP6, so I disabled it, and now nslookup finds server localhost 127.0.0.1, but still no worky.

Still same nondescript SERVFAIL error, but nothing else. Is there an 'established' rule to allow any outbound requests (other than http and https) to the 2008 server?

I have gone through every website I can find, and the usual answers mention refreshing dependencies (Which I believe fixes it for manual deployment, but not for automatic) and removing the source control coding from the projects, which hasn't helped me.

The error does not occur every time I build, but it seems random on different deployment projects each time.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.And it came on even if I set all projects to be build in a current configuration and the setup project not to.Does anyone have any advice on why exactly this error occurs and how to go about fixing it?This is a known issue in Visual Studio 2010 (a race condition). We've run into this as well, and had a very unsatisfying support call on this issue with Microsoft.Even so, I added a rule to explicitly allow TCP/UDP port 53 from this server.