Yes. it will work as a standard secondary. It's clearly not the preffered
configuration as an AD integrated configuration.
It is important to have the users (computers) configured to use this
secondary DNS server as a client DNS secondary client. Because this is a
Standard secondary, it is read only and workstations can not register or
update DNS records using this server.
It is also subject to the DNS transfer time-outs which will cause you
problems if the SBS server is down for extended periods or other zone
transfer problems creep up.
Ryan wrote:
> Lanwench [MVP - Exchange] wrote:
>> Ryan <> wrote:
>>> My goal is just DNS redundancy. I don't want it to be a domain
>>> controller, but rather just replicate the DNS.
>>
>> It can't.
>>> I don't have my SBS server go down often, but it does every now and
>>> then and while the server is being rebooted my users have no way to
>>> access the internet for whatever they may need since the only DNS
>>> server in their DHCP scope is in the process of restarting.
>>>
>>> As I stated before it doesn't happen often. I figured out what I
>>> wanted though by forwarding zones to my new Server 08 box and
>>> setting up DNS on it. Seems to be doing the trick.
>>
>> I'm not sure how this can be working as you describe - can you be
>> more specific?
>> Be very very careful with DNS in an AD environment. You can break
>> stuff.
>
> I logged into SBS and fired up the DNS console and set the properties
> of my local forward lookup zone up for domain transfers "to DNS
> servers in the nameserver tab", and I added my other DNS servers IP
> to that nameserver tab
>
> I also set replication (general tab) to "any DNS server in the domain:
> domain.local" rather than "to any DC in the domain: domain.local".
>
> Then on the "Secondary DNS server" I added the local zone as a
> "secondary zone" pointed it to the "Master" nameserver and it
> replicated the zone off the master server.
>
> I did the same for PTR records too.
>
>
>>>
>
>>>
>>> Lanwench [MVP - Exchange] wrote:
>>>> Ryan <> wrote:
>>>>> I'm presently configuring a Server 2008 box for SQL in our office.
>>>>> I've got a SBS 2003 SP2 box as our AD/DNS/DHCP/Exchange server and
>>>>> I'd like to configure this new one as a secondary DNS.
>>>>>
>>>>> Could anyone point me to some documentation on how to configure
>>>>> both the SBS 2003 to allow DNS replication and for Server 2008 to
>>>>> pick it up?
>>>>> Thanks,
>>>>> Ryan
>>>> It would need to be a domain controller if it were to run
>>>> AD-integrated DNS. I don't think you can have a W2008 DC in an
>>>> SBS2003 domain, but you should ask in
>>>> microsoft.public.windows.server.sbs. What's your goal? Are you
>>>> really concerned that your SBS box is
>>>> going to be down on a regular basis, disrupting users' ability to
>>>> surf? If so, I'd probably see what I could do to stop the SBS box
>>>> from being down during business hours.
--
/kj
|