We are using Windows Active Directory, DNS on 2 servers, but DHCP is on just
one of them. I can have The Network Guy look into it.
OTOH, both servers involved are virtual servers within a single physical
server. So if the physical goes . . .
On Wed, Nov 3, 2010 at 2:44 PM, Tom Jedrzejewicz <tomjedrz@xxxxxxxxxxxxxx>wrote:
On Wed, Nov 3, 2010 at 6:56 AM, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx
One point about this. If I assign 192.168.0.34 toi
ricoh1.dilgardfoods.local, and my System i printer definition references
ricoh1.dilgardfoods.local, then the DNS server must be up for the System
to see the printer, right?
If the DNS server is another box and it's down, is the printer then
unreachable from the System i?
We have a Windows server doing DNS.
As pointed out in subsequent posts, it is advisable to have multiple DNS
servers accessible, for just this reason.
If you have Windows DNS, presumably you have Active Directory. Common,
recommended (I am not going to say "best") practice is to have 2 Domain
Controllers. It is easy to set them BOTH to serve DNS and DHCP, and they
keep themselves synchronized to each other. Problem solved.
This is the PC Technical Discussion for iSeries Users (PcTech) mailing list
To post a message email: PcTech@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: PcTech-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives