Domain Controller DNS Query Refused

  • Thread starter Thread starter Wolfdog
  • Start date Start date
W

Wolfdog

I have spent the last three days working on this issue and im stumped.

I am setting up a domain controller on windows server 2003 Enterprise
R2. Everything is actually working perfectly. The DNS resolves just
fine I can add and remove computers from the domain. It all works fine
until I restart a client machine.

After the client computer restarts and I enter username and password
it attempts to log into the Domain Controller (Active Directory) but
it cannot resolve the domain DNS information. If I run nslookup on the
client for any A record or try a zone transfer 'ls' I get "Query
Refused". The odd part is that if I walk over to my DC server and run
nslookup on any A record it works. Then I can walk back over the the
client and all the DNS works. Then I can logout of the client machine
and log back into it and everything works just fine. Then if I restart
or shutdown the problem repeats itself. Also when things are working
on the client I can do zone transfers with nslookup (I have opened up
zone transfers because I thought that might be the problem).

It also gets a little more interesting, if I have two clients (they
both have the problem), I can get one working (with the method above)
then start the other machine. When the new client has the "Query
Refused" problem I can walk over to the working client and open
internet explorer then it goes to google or the set default home page.
Then I walk over to the client that has been reciving "Query Refused"
and the problem is gone. Everything works, as if nothing ever went
wrong.

In the case that I don't go to another machine and resolve a name on
the DNS server the client will sit with DNS only returning "Query
Refused". I have let it sit for hours curious if it was just a time
issue.

I have no idea what the problem may be, anyone else ever experience
this?
 
I have spent the last three days working on this issue and im stumped.

...
Click to expand...

I am so imbarressed, I continued adding my client machines to the
domain controller and my next machine was my laptop over a wireless
connection. For the wireless I am using a router I had lying around
that is used as an access point. When I connected my laptop to the
wireless my domain controller panicked and reported that there is an
IP conflict on the network.

The Solution: My router was set to the same static IP address as my
Domain Controller (I set up the router 6+ months ago and forgot about
it)

If anyone might know is there perhaps an explination to this did the
client connect to the router after restart then when anyother machine
connected to the DNS the switch knew where to send the packets?
 
Wolfdog said:
I am so imbarressed, I continued adding my client machines to the
domain controller and my next machine was my laptop over a wireless
connection. For the wireless I am using a router I had lying around
that is used as an access point. When I connected my laptop to the
wireless my domain controller panicked and reported that there is an
IP conflict on the network.

The Solution: My router was set to the same static IP address as my
Domain Controller (I set up the router 6+ months ago and forgot about
it)

If anyone might know is there perhaps an explination to this did the
client connect to the router after restart then when anyother machine
connected to the DNS the switch knew where to send the packets?
Click to expand...

The client arps in order to resolve the IP address to MAC address. If
the router responds first, the DNS query will be sent to the router. If
the Server responds first, the query will go to the server. I'm
surprised you didn't get a notice of the conflict.

....kurt
 
Back
Top