Those names have no meaning or use for any of your clients. What those
names allow is that FROM YOUR i you can telnet, ping, ftp, whatever to
either of those four names and still end up at 192.168.0.1.
If your windows clients truly are using your i as their dns then you
should be able to
- do this from your client
Start, Settings, Network Connections, Local Area Network, Properties and
see how it obtains the address of the DNS. Granted I haven't quite
grasped getting the address of your DNS automatically.
- do this from your client to check out the configuration on your server.
Start, Programs System i Access for Windows, System i Navigator, Network,
Servers, DNS and actually see something in there. We have one lpar
serving up dns for our dmz and beyond. The rest of our DNS' are Windows
based.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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
