On Tue, Jul 14, 2009 at 18:31, Jeff Crosby<jlcrosby@xxxxxxxxxxxxxxxx>
wrote:DCs that are also DNS
1) Netserver properties has a Domain Name attribute, which now says
DILGARD. The domain will be called dilgardfoods.local. I assume this
attribute needs to be changed to dilgardfoods.local. Correct?
No. It is recommended that you change this to a value which is _NOT_
your NetBIOS Windows-Domain Name (The Netbios-Domain Name is the one
you can select in the Domain-Dropdown Field on Windows XP, or the one
you need to prefix your Username with in Windows Vista e.G.
ACMT\l.beeler).
Now, you can change it to your domain name and should not suffer any
ill effects, in fact it will enable you to browse the network.
Browsing however is being faded out.
Are you deploying WINS in your new domain, or are you running
DNS-only? If you're running WINS, it will make sense to add the
appropriate WINS servers to the netserver configuration.
2) Does the DMNNAME parm of the CHGTCPDMN command need to be changed
from dilgardfoods.com to dilgardfoods.local? Or does this 'domain'
have no relation to a Windows domain?
It does not need to be, but it makes sense to ensure the appropriate
DNS records are inserted into the dilgardfoods.local zone, and the IBM
i instance reconfigured to use the DNS serves which also host the
dilgardfoods.local zone (most probably your DCs). Then, you can change
the domain name of your i.
Remember, these are general statements. I don't know exactly what kind
of software you're using or what your usage cases are. For most modern
applications, DNS is extremely essential for even the most basic
functionality. So, misconfiguring DNS can lead to serious downtime
(which is why it is recommended to have at least two DCs hosting DNS).
As such, do not take my reply as a to do list and verify first which
of the applications running on your i require DNS to configured in a
specific way. The most obvious choices here are MSF/SMTP and the
webserver.
midrange.com
