> 1 - Does the new DNS server have to be an AD controller?
No, unless you want the zone to be AD-integrated.
2. If all you are doing is moving DNS from one server to the other, there
should be no reason to involve the ISA server. The ISA server would come
into play IF you are publishing this DNS server to the outside world. This
means if this server is the one that will answer my server when my server is
looking for (say) your MX record, then you are most likely publishing it
thru your ISA server. So, in that case, what you need to do is change the
IP/name of the published/destination server in ISA. I think you know what
I'm talking about.
As for the clients, if they are all getting IPs from DHCP, then you just
need to modify your DHCP scope to now include the IP of this new servers as
the DNS server. If you are not using DHCP, then you have a long task in
front of you, and yes, you have to manually (or programmatically) update the
DNS IP on the clients. BUT, since ISA will still remain on the original
server, then no need to change the Default Gateway.
HTH
--
Sincerely,
Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
"Jeroen Jordens" <jeroenj_REMOVE_@morcomm.co.nz> wrote in message
news:45ec01c3e476$61884420$(E-Mail Removed)...
> Hi,
>
> After unsuccessfully attempting to fix a DNS server that
> has multiple NIC's, DNS will be shifted to another
> machine. There's a 'server' on the LAN running SUS, so
> this beast is picked to do the honours.
>
> What I need to know is this:
> 1 - Does the new DNS server have to be an AD controller?
> 2 - ISA & Internet connection will remain on original
> server. How do I set up forwarders? Do I set a default
> gateway in (client) TCPIP that points to the ISA server,
> with DNS pointing to the new DNS server? Then a forwarder
> in DNS pointing to the ISP or to the ISA server?
>
> Thanks,
> Jeroen
>
>
Similar Threads
