Re-install DNS on W2kServer

[n]

Hello,

First off, I know minimal about the construct of a DNS and realize
that I should first do my homework befor posting... however for the
sake of expediancy it is necessary to post.

I have a W2kServer, with the most recent service pack. The work
stations at one time could access various web sites, including the
companies own site (located off site), and send emails to various
domains, and all of a sudden no longer can. I have checked for the
usual viruses and worms and have turned up with nothing. I am
hesitant to go poking around in the DNS since i dont understand it
well enough. Can I, some how, uninstall and re-install the DNS
without harming the rest of the system (since i understand that the
DNS is an integral part of W2k Server and Active Directory)?

Thank you in advance for looking at my question.

Respectfully,

NB

 

[Ace Fekay [MVP]]

In

Hello,

First off, I know minimal about the construct of a DNS and realize
that I should first do my homework befor posting... however for the
sake of expediancy it is necessary to post.

I have a W2kServer, with the most recent service pack. The work
stations at one time could access various web sites, including the
companies own site (located off site), and send emails to various
domains, and all of a sudden no longer can. I have checked for the
usual viruses and worms and have turned up with nothing. I am
hesitant to go poking around in the DNS since i dont understand it
well enough. Can I, some how, uninstall and re-install the DNS
without harming the rest of the system (since i understand that the
DNS is an integral part of W2k Server and Active Directory)?

Thank you in advance for looking at my question.

Respectfully,

NB

I really don't think it's something that reinstalling DNS will fix. This can
cause more problems if not done right especially in a production
environment. How long ago did this start? Was anything changed?

It *may* be due to the new Verisign changes to the .com and .net namespaces,
but need to know more of what your configuration is. Pointing to your own
DNS and using forwarding? That's the proper recommendation.

Try a couple tests if you can resolve the domain names you are trying to get
to, such as pinging by it's name. You can also use nslookup or Dig.

nslookup
set type=mx
thedomainnameinquestion.com

And that should return the mail server's name. Then try to ping it by name.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Steve Duff [MVP]]

There are very few problems you can fix with
a shotgun. And I doubt this is one of them.

But you sure can do a lot of damage with one,
especially in the dark.

Find out what your problem is first, and then fix that.

If you think your problem is DNS-related, then do
a ping by name. If you get a "no such host" then
the DNS lookup is failing, and you have to dig deeper.
If you get a different error ("unreachable", etc.), or the ping
actually works, your problem is something else.

Steve Duff, MCSE
Ergodic Systems, Inc.

 

[Ace Fekay [MVP]]

In

There are very few problems you can fix with
a shotgun. And I doubt this is one of them.

But you sure can do a lot of damage with one,
especially in the dark.

<snip>

Good analogy.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[n]

Thank you all, I will test it out in the following day and notify you
of my findings. I appreciate the leads and the insight.

Respectfully,

NB