G
Guest
Hello all,
I have just taken over a network with the following issues:
1. DNS W2K reading event ID: 3000
2. Doing an NSLOOKUP IP-ADDRESS gives me the name of a server
"wrong-server-name" neither in use nor on my network! Doing the NSLOOKUP from
the DNS server CMD prompt gives me the same answer.
I go into the DNS console and the entry is in for "correct-IP-address" =
"correct-server-name" is in as a record, but the NSLOOKUP tells me something
different. I have also issued the IPCONFIG /FLUSHDNS for the boxes with no
joy.
3. I have now been told not to reboot my DNS box by my old counterpart (he
now works elsewhere). Because the DNS records will revert back to January
07??
We have trusts to other domains/companies and the DNS is quite extensive so
I'm loathed to reload/clear cache the DNS incase it all goes wrong!
Future plans will: Built a secondary DNS server.
However for the now, how can I fix the above problem, I have a felling all
my symptoms are tied together somehow, I just don't know where?
Thanks.
I have just taken over a network with the following issues:
1. DNS W2K reading event ID: 3000
2. Doing an NSLOOKUP IP-ADDRESS gives me the name of a server
"wrong-server-name" neither in use nor on my network! Doing the NSLOOKUP from
the DNS server CMD prompt gives me the same answer.
I go into the DNS console and the entry is in for "correct-IP-address" =
"correct-server-name" is in as a record, but the NSLOOKUP tells me something
different. I have also issued the IPCONFIG /FLUSHDNS for the boxes with no
joy.
3. I have now been told not to reboot my DNS box by my old counterpart (he
now works elsewhere). Because the DNS records will revert back to January
07??
We have trusts to other domains/companies and the DNS is quite extensive so
I'm loathed to reload/clear cache the DNS incase it all goes wrong!
Future plans will: Built a secondary DNS server.
However for the now, how can I fix the above problem, I have a felling all
my symptoms are tied together somehow, I just don't know where?
Thanks.