Click here for important information about

Reverse Lookup Issues

December 27, 2010 at 11:04:41
Specs: Windows Vista, Quad Core / 2Gig
I am having a problem. Our DBA is using SQL Server 2005 running an Access front end because the systems were developed in Access and migrated later to SQL Server. The SQL Server uses Windows Authentication but will fail through out the day and the user has to log out and back in (on some computers not all). Our DBA says the problem is a reverse lookup issue. On the failing computer, if you run...

ping svrname

it resolves the name to an IP and pings fine. If you run...

ping -a

it does not resolve the server name but does ping. It does work on other computers just not this one.

I have never setup a reverse lookup zone in our DNS because I did not think we needed one but fine I did it. The problem now is I am getting the following error...

The DNS server encountered error 32 attempting to
 load zone from Active
 Directory. The DNS server will attempt to load this
 zone again on the next timeout cycle. This can be
 caused by high Active Directory load and may be 
a transient condition.

For more information, see Help and Support Center 

When I click the Support Link it simply says Microsoft has no solution to this problem yet. Can any one help us?

See More: Reverse Lookup Issues

December 28, 2010 at 10:45:59
Ok, solved the problem. I did an NSLOOKUP and found it was not resolving the DNS server name. After much triel and error I found that you I had to do a SERVER mydnsservername on the NSLOOKUP of the DNS server.

This has at least resolved the DNS issues but I have a feeling that the SQL Server problem has to do with us switching Default Gateways on the DHCP server because our primary router is crapping out and we are switching to the backup router. The problem is that I put in a static route on the server to route traffic to the second NIC on our SQL Server for any traffic coming from our backup router but the DNS Host record was still set to the IP of the old NIC. I am going to change the DNS entry and see if it solve the SQL Server problem.

Thanks for listening.

Report •
Related Solutions

Ask Question