I have a couple of issues going on.
I am working on a network which has the IPSs DNS servers listed on the name
server tab on the forward lookup zones.  The DC is able to resolve websites.
When I take the DNS servers out of the Name Server listing and add them as

I have a IP subset 203.195.112.62 to 203.195.112.120.  The subnet mask is
255.255.255.0.  I am running a Win2000 DNS server on my network.  I add a
new zone to the DNS server, say ( abc.com ) and also I have created a
112.195.203.in-addr-arpa zone.  I have added a A record to the ...

What is the cached lookups in the DNS tree?  Are these lookups necessary?  I
currently have only one .(root) in mine, is this safe to delete?  I don't
remember seeing these types of items before in my DNS server, but my network
seems to be slowing down later in the day.  Just ...

I have this really weird problem.  
We have been seeing a strange issue with some Windows servers today. We
currently have three servers that are blue screening at boot up with the
following error:

I needed to dcpromo /forceremoval a domain controller in an existing forest
due to replication problems and dns issues. I removed most of the meta data
from the other domain in the forest except the data that is producing the
following errors.

Current configuration is a legacy (unix) dns hosting 'xyz.com'. I have a
Windows 2000 AD domain hosted as 'abc.xyz.com'.
We would like to host the parent domain (legacy zone 'xyz.com') on the
Windows DNS server.

All,
I am finding it really hard to find a definitive answer to whether I
need Reverse Lookup Zones in my AD. I currently have them, but they
are messey. Some live in the empty root, some are delegated to the

Is there a way to export all my current DHCP settings to a text file
for import into excel?
thanks
Rick

We have a recurring problem whereby a secondary zone disappears every few
months.
We are running a 2 domain forest. Domain 1 is running mixed 2000 and 2003
servers, Domain 2 is 2003 only. we setup the domain 2 dns zone as a

We have an Exchange server that is configured with a static IP address
but every few days or so, its IP address changes in the DNS. So all of
the sudden no one can connect to the Exchange server as the DNS is
giving out an incorrect IP address while the sever still has its

I have changed my Win2K server's IP address from 192.168.1.4 to
192.168.21.10. I have also changed the IP addresses of the two PCs on
my LAN.
When I ping 192.168.21.10 is works fine. From Windows Explorer, I am

I'm unable to figure out where ip 192.168.21.200 is stored in DNS server. I
cleared cache, restarted server, refreshed nothing is working.
Please help.
Thanks