No, you do not need a new DNS zone. You should probably make a new AD site
for this subnet. and use ad intergarted DNS to use AD to replicate between
the two dns servers.
DHCP is a pretty straight foward server, it usually just works. I got
nothing there.
"JBLaze" wrote:
> Hello.
>
> Here's the situation. The company i work for is moving its warehouse
> to a new building. I've just started to get the network up and running
> at this new location. I have a window 2003 standard server in place to
> start with. I configured it while at the old building to be a Domain
> Controller. After placing it at the new location I added both the DNS
> and DHCP server role. AD replication is working fine but I am a little
> unsure about the best way to configure DNS at this new Site. These
> locations are on diffrent subnets. SITE A (OLD) is a 16 bit network
> and SITE B (NEW) is a 24 bit network. Should I create a new DNS zone
> for SITE B???
>
> Also, DHCP is not working for this server. I authorized the server and
> activated the scope. I checked the event logs and it says that 'this
> server is now authorized to service clients', but none of the clients
> can get an ip address offered. The DHCP stats indicate that the server
> is receiving requests but not leasing addresses. I went ahead and
> configured the firewall at SITE B as DHCP and it is working fine, but
> eventually would like the DC to handle DHCP. Also SITE A has a working
> DHCP server, could this be causing a conflict.
>
>
> Thanks A Lot for your help.
>
>
|