WISPguy
Da WiFi Guy
Posts: 1393
Age: 36
Loc: Kansas, USA
Reg: Tuesday September 21st 2004
|
Tuesday July 13th 2010 11:35 AM - Post#99921
I seem to have a DNS issue on my internal network. I noticed it when I was trying to get a freshly installed machine to install/update software via a GPO. The event log kept saying that no domain controller was available for my domain. However, I could log in with my network credentials. At some point I got the idea to ping 'mydomain.com' and see what IP it came back as. Well, it came back with an IP not belonging to a domain controller or DNS server. Thinking that was odd, I tried from a different machine, same result except with a different IP. I tried a couple more machine, only to find that they were coming back with different IP's. I am not very familiar with windows DNS, but that seems wrong to me. The fact that I am experiencing some other issue that could be the result of improper DNS configuration tells me that it probably is wrong. Any ideas? Resources?
"Two things are infinite: the universe and human stupidity; and I'm not sure about the universe."
- Albert Einstein 
 |
|
 Hardrive
DLT Staff
Posts: 13738
Loc: Long Beach, CA
Reg: Thursday January 4th 2001
|
Wednesday July 14th 2010 10:48 AM - Post#99922
In response to WISPguy
your going to get odd results trying to ping or nslookup only a domain name. use a host name.
make sure your workstation can ping the domain controller by host and domain name and that the workstation is getting its dns from your local dns server: ipconfig /all
from the workstation: ipconfig /flushdns
|
WISPguy
Da WiFi Guy
Posts: 1393
Age: 36
Loc: Kansas, USA
Reg: Tuesday September 21st 2004
|
Wednesday July 14th 2010 11:31 AM - Post#99923
In response to Hardrive
I tried all that. No problems pinging the DNS servers or the Domain Controllers, which are actually the same machines. One is a Win2K Server and the other is a Win2K3 box.
"Two things are infinite: the universe and human stupidity; and I'm not sure about the universe."
- Albert Einstein
|
|
Hardrive
DLT Staff
Posts: 13738
Loc: Long Beach, CA
Reg: Thursday January 4th 2001
|
Monday July 19th 2010 04:32 PM - Post#99935
In response to WISPguy
so the dns settings on the workstation are pointing to the dns server?
|
matt619
enthusiast
Posts: 880
Loc: San Diego, CA
Reg: Wednesday February 12th 2003
|
Tuesday July 20th 2010 09:05 PM - Post#99942
In response to WISPguy
The only thing that's coming to mind is a misconfigured forward lookup zone?
| The bigger the government, the smaller the citizen. |
|
 Fortch
Da Mechanic
Posts: 3688
Age: 40
Loc: Redondo Beach, CA
Reg: Saturday June 29th 2002
|
Wednesday July 21st 2010 01:08 AM - Post#99944
In response to WISPguy
Are you pinging the FQDN? Have you run netdiag? Can you open the domain's netlogon share from the client, then run gpresult /r?
Windows DNS is pretty straight forward -- make sure your SRV records are accurate, and see if the timestamps on the affected A records are the same on both DCs...you may need to clear your DNS cache there too.
| "...passwords are a lot like underwear, you don't leave them laying around or hanging on the corner of your computer monitor, you change them frequently, you don't swap them with your friends or strangers and get some new ones on a regular basis" --Lanwizard |
|
WISPguy
Da WiFi Guy
Posts: 1393
Age: 36
Loc: Kansas, USA
Reg: Tuesday September 21st 2004
|
Wednesday July 21st 2010 09:12 PM - Post#99946
In response to Fortch
I am starting to see that I have something wrong/corrupt somewhere. I setup a couple Linux boxen and one of their IPs resolves to an entirely different hostname. Got some digging to do. ;-)
"Two things are infinite: the universe and human stupidity; and I'm not sure about the universe."
- Albert Einstein
|
|
