Re: Odd DNS Issues: Please Help
From: Herb Martin (news_at_LearnQuick.com)
Date: 06/18/04
- Next message: jtaylor: "Computer account removal"
- Previous message: Mark McCurdy: "DCPromo"
- In reply to: Jeremy_at_gilbarco: "Re: Odd DNS Issues: Please Help"
- Next in thread: MJC: "Re: Odd DNS Issues: Please Help"
- Reply: MJC: "Re: Odd DNS Issues: Please Help"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 18 Jun 2004 15:00:20 -0500
"Jeremy@gilbarco" <anonymous@discussions.microsoft.com> wrote in message
news:1e7ac01c4556d$77153010$a501280a@phx.gbl...
> If it's giving you the "unknown" then it seems to me you
> are not able to reverse resolution either. Since it's able
> to reach a DNS server (since there is some response, not a
> time out) I would guess that your zone files/AD stuff is
> broken some how.
No, this is (almost) totally an irrelevant artifact of the
NSLookup tool.
Most people don't need the reverse zones for internal use
anyway.
> You may want to turn on detailed logging
> so you can get more information. Check your event logs. Do
> you have other DNS servers in this environment or is it
> your only box?
It's usually simpler to just go set them up right -- there are
only a few things that go are likely to be wrong and detailed
logging will likely be too much information for someone who
cannot just go check the DNS servers and clients NIC settings.
DCDiag.exe, output sent to a text file to search for FAIL, WARN,
and ERROR will likely give more useful info -- which can be
posted here easily if the problems are not resolvable immediately.
-- Herb Martin > > > >-----Original Message----- > >"MJC" <MJC@mjc.com> wrote in message > >news:uylATaWVEHA.3788@TK2MSFTNGP12.phx.gbl... > >> I recently upgraded my Windows 2000 DNS server to > Windows 2003, All seemed > >> fined at first except for the following: > >> > >> - Intermittently, I receive calls that Active Directory > logins are slow. I > >> check DNS and the service is running but my DNS server > cannot resolve > >itself > >> and others. > > > >Check you server and make sure that it's OWN CLIENT NIC > >settings point ONLY to the internal DNS server set. > > > >(If you need to resolve "The Internet" then you use the > Forwarder > >tab on the DNS server properties.) > > > >Make sure that ALL clients (servers are clients too) are > set to > >ONLY use the internal DNS server (set.) > > > >Make sure that the internal DNS Primary (or AD- > integrated) servers > >are set to ALLOW DYNAMIC UPDATES (or secure updates) for > >the zone. > > > >> - When I do a NSLOOKUP this is what I get: > >> server: unknown > >> 10.18.1.32 (which is the IP of my server) > > > >That is an irrelevant error generated by NSLookup which > may > >be safely ignored. (Really -- it is just an NSLookup > artifact.) > > > >The key is if the following information -- the actual > resolution -- > >works or not, and gives the correct info if it works. > > > >> If I restart the service, everything works fine. Any > ideas would be > >helpful. > > > >What Service Pack etc? What clients? > > > >If you have legacy clients, you might have a WINS/NetBIOS > problem (too.) > > > >-- > >Herb Martin > > > > > >> > >> Thank you, > >> > >> Mike > >> > >> > > > > > >. > >
- Next message: jtaylor: "Computer account removal"
- Previous message: Mark McCurdy: "DCPromo"
- In reply to: Jeremy_at_gilbarco: "Re: Odd DNS Issues: Please Help"
- Next in thread: MJC: "Re: Odd DNS Issues: Please Help"
- Reply: MJC: "Re: Odd DNS Issues: Please Help"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
