Re: Tough DNS Problem
From: William Stacey [MVP] (staceywREMOVE_at_mvps.org)
Date: 04/22/04
- Next message: Danny Sanders: "Re: Replacing W2K DC server with W2K3 DC server"
- Previous message: Christopher Beard: "Re: Tough DNS Problem"
- In reply to: Christopher Beard: "Re: Tough DNS Problem"
- Next in thread: Rick Chisholm: "Re: Tough DNS Problem"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 22 Apr 2004 13:40:53 -0400
www.mvptools.com. You need the .net framework 1.1 installed to use. dig is
at www.isc.org. dig may be a little more complex as you need to install the
bind nt build just to get the dig.exe and its required dlls. You could also
extract them I think, but not sure and you need to know what dlls to grab -
I think about 3-4. If you have the framework on one client, pull down
netdig as just one exe (actually two as it has a console and gui version.)
Cheers!
-- William Stacey, MVP "Christopher Beard" <c.beard@pharmco.com> wrote in message news:2d8f01c4288f$a6343450$a401280a@phx.gbl... > Where do I find netdig? Can you email me at > c.beard@pharmco.com? Thanks for your help! > > >-----Original Message----- > > > >Use something like dig or netdig and do "netdig > mydomain.com any". What do > >you see? > > > >-- > >William Stacey, MVP > > > ><anonymous@discussions.microsoft.com> wrote in message > >news:2cd401c4288c$dc583fc0$a601280a@phx.gbl... > >> Just the two internal DNS servers for Active Directory. > >> These DNS servers forward the requests of Internet > >> addresses. > >> >-----Original Message----- > >> >From that client, do an ipconfig /all. What dns > servers > >> are configured? > >> >Do you have *only the ad dns servers in the list and > not > >> any ISP dns > >> >servers? > >> > > >> >-- > >> >William Stacey, MVP > >> > > >> >"Christopher Beard" > >> <anonymous@discussions.microsoft.com> wrote in message > >> >news:2d3d01c42884$947a3e90$a501280a@phx.gbl... > >> >> I'm having a really tough issue with DNS - I > support 4 > >> >> sites all of with use our DNS servers and at one of > our > >> >> sites, clients can no longer resolve names through > DNS. > >> >> This results in 10 minuit login times for the users. > >> All > >> >> was working well before yesterday, and nothing has > >> >> changed recently. The clients all have the correct > DNS > >> >> server addresses in their TCP/IP settings. Using a > port > >> >> scanner from one of the failing computers, I was > able > >> to > >> >> verify that port 53 is open on both DNS servers. I > ran > >> >> the NETDIAG tests on the same computer and received > no > >> >> errors (even DNS tests passed) however, it gave me > the > >> >> following warning: "[WARNING] Cannot find a primary > >> >> authoritative DNS server for the > >> >> name 'kc0015.pharmco.com.'. [ERROR_TIMEOUT] The > >> >> name 'kc0015.pharmco.com.' may not be registered in > >> DNS." > >> >> All other sites are resolving names properly to the > >> same > >> >> DNS servers. Does anyone have any ideas? > >> >> > >> >> > >> >> > >> > > >> >. > >> > > > > >. > >
- Next message: Danny Sanders: "Re: Replacing W2K DC server with W2K3 DC server"
- Previous message: Christopher Beard: "Re: Tough DNS Problem"
- In reply to: Christopher Beard: "Re: Tough DNS Problem"
- Next in thread: Rick Chisholm: "Re: Tough DNS Problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|