×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
DNS does not need to be on a windows server. It would be best to have two Domain Controllers. If you lose you DC you are up a creek without a paddle so a second DNS server won't help. Think about adding a second DC to your network.
--
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Monday, February 27, 2017 10:51 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: What are you using for CHGTCPDMN INTNETADR (DNS servers) parm?
On Mon, Feb 27, 2017 at 1:41 PM, Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>
wrote:
Correction as my number two key does not seem to want to work today.
(Lazy finger I think.)
" For internal, you should have at least one for each subnet within your
organization. If you have only 1 subnet then you should have TWO DNS
servers on that subnet."
We have only 2 Windows servers, period. The domain controller and a
terminal services server. You're suggesting the latter should also serve
up DNS?
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
