At 4/5/01 06:18 PM -0500, you wrote:
OK. I got all that. But, as I replied to Gerald who was also kind enough to point me in the right direction, and before I try to implement this, I have one other question: If I enter static IP addresses for all the client machines on the Qube, doesn't that prohibit me from using DHCP to assign their IP addresses? Or, does the IP address not need to resolve to the machine's actual network name? That is, does the IP just need to be listed in the hosts table?
Whoops. I already answered that message. But specifically no, what the machine considers its network name to be has nothing to do with DNS, and the Qube could not possibly care less what the machine thinks its name is. (Note that this saves you a lot of grief should Wynona W. Williams on your network choose www as her machine's hostname...)
The client machine does use its network hostname (what *it* thinks its name is) to identify itself to programs like sendmail (as in EHLO WWW.DOMAIN.COM). However, sendmail knows this can be spoofed and basically ignores it for authentication purposes.
DHCP will be fine. Matter of fact, DHCP is the reason I learned from our ISP to use generic names like "ip-0-1" rather than "joe" since joe may have a different IP tomorrow.
However, I did make a comment about not having these sorts of problems with the old Qube 2, but that was a purely subjective opinion - as in it SEEMS to me that I didn't have these sorts of issues with the Qube 2. Which is why I asked if others were seeing the same sort of thing.
I think I had that problem with the Qube2. Don't remember (if I did, fixed it a long time ago). Those entries are all over my /etc/hosts file anyway, since bugs the hell out of me to see billions of log messages saying "Unable to get canonical name of..."
-- Rodolfo J. Paiz rpaiz@xxxxxxxxxxxxxx