R
Rodge
I have recently enterred a new position with a new company. The environment I
have come into has been put together by several different people, most of
which don't have the ideal tech background. I'm am slowly trying to figure
out just how everything has been setup and of course what changes will affect
what. There is a problem with DNS on my local subnet. On Friday I got around
this so that folks here could get their email(the exchange server is in
another city) by pointing the clients to a secondary DNS box. The local
domain controller runs active directory and dns, but it is a windows 2000
machine, not a windows 2000 server. Not ideal, but I have seen this before. I
also notice that they are using forwarders in the dns snapin for their local
domain. I've never had to use forwarders before, but can't say that I know
this will cause any issues. On the local AD/DNS box under nic properties,
they only have the local ip address for the box itself listed for dns. I've
seen this setup this way before, but typically there is a secondary domain
controller running dns with that ip listed in the nic properties as a backup.
This environment has 6 sites. Since each site is using 192.168 addresses, I
believe there is a vpn involved somewhere, but haven't been able to verify
that yet.
The domain controller at the main office(using 192.168.3 subnet) is running
server 2003 R2 sp2. I have used this as a temporary dns backup for local
clients. There is just one local domain(and zone) setup. There are no reverse
zones setup.
My question is simply this, is this forwarder necessary or even a good
practice?
Zone trasnfers are not setup.
My thoughts on setup would be to list the local dc's ip address as the
primary dns and list the main office dc's ip address as a secondary. Ideally,
I would like to have a second DC running dns as well, but that is in the
future. For now, I'd just like to get the local dc providing reliable dns.
Right now I see event id 5781 about every 2 hours in the event log.
have come into has been put together by several different people, most of
which don't have the ideal tech background. I'm am slowly trying to figure
out just how everything has been setup and of course what changes will affect
what. There is a problem with DNS on my local subnet. On Friday I got around
this so that folks here could get their email(the exchange server is in
another city) by pointing the clients to a secondary DNS box. The local
domain controller runs active directory and dns, but it is a windows 2000
machine, not a windows 2000 server. Not ideal, but I have seen this before. I
also notice that they are using forwarders in the dns snapin for their local
domain. I've never had to use forwarders before, but can't say that I know
this will cause any issues. On the local AD/DNS box under nic properties,
they only have the local ip address for the box itself listed for dns. I've
seen this setup this way before, but typically there is a secondary domain
controller running dns with that ip listed in the nic properties as a backup.
This environment has 6 sites. Since each site is using 192.168 addresses, I
believe there is a vpn involved somewhere, but haven't been able to verify
that yet.
The domain controller at the main office(using 192.168.3 subnet) is running
server 2003 R2 sp2. I have used this as a temporary dns backup for local
clients. There is just one local domain(and zone) setup. There are no reverse
zones setup.
My question is simply this, is this forwarder necessary or even a good
practice?
Zone trasnfers are not setup.
My thoughts on setup would be to list the local dc's ip address as the
primary dns and list the main office dc's ip address as a secondary. Ideally,
I would like to have a second DC running dns as well, but that is in the
future. For now, I'd just like to get the local dc providing reliable dns.
Right now I see event id 5781 about every 2 hours in the event log.