Resolving search lists doesn't mean they have to be configured correctly "everywhere". Just for the server and the client involved in the current problem. That is to say while it needs to be configured "everywhere" to make each client work when their turn comes in the schedule it is a red herring to suggest that you need to concern yourself with that "everywhere" when troubleshooting a specific issue. If there's been an "everywhere" change it will become apparent due to the fact that most of the clients will fail. That kind of global failure due to bad planning can occur regardless of which method you use. (e.g. What happens if all your FQDNs are suddently invalid due to a domain name change?)
In a related point: If you use short names and search lists then you don't have to go edit all your policies with new domain names if they change (and on occasion they do especially in mergers/acquisitions). You just have to edit the resolv.conf on each of the servers and clients. That can be easily scripted (as in fact it was here recently when we swapped out decommissioned named servers for new ones). In the very few cases where I've thought difference between searched name and FQDN might be a problem I've addressed it by adding entry to master/media server hosts file and the specific client. ________________________________ From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ed Wilts Sent: Monday, March 16, 2009 3:07 PM To: Stafford, Geoff Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] question on client names On Mon, Mar 16, 2009 at 12:28 PM, Stafford, Geoff <gstaff...@barclaycardus.com> wrote: The need to use FQDNs is, imho, a sign that you don't trust your DNS. I trust the DNS - I have extensive DNS experience and our company would be down without a fully functioning DNS infrastructure. Ours works. FQDNs are a PITA if you ask me and I would rather take the time to make something as mission critical as DNS work right instead of hiding the real problem. FQDNs make it absolutely clear what's going on. Remember, you can't do a backup using a short form name anyway - internally, you're resolving to a fqdn whether you like it or not. You're not only relying on FQDNs, but you're also relying on the search lists configured properly everywhere. You can take all the short cuts you want, but not taking the short cuts saves you headaches later, as MANY people have found out. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org Please consider our environment before printing this e-mail or attachments. ---------------------------------- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. ----------------------------------
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
