One benefit of FQDNames: If you try to backup (or restore) MyNode it will also backup MyNode1, MyNode2 , MyNodeAlso, MyNodeNot and anything else which starts with the same word. (I don’t get to control what my client nodes are named). With a FQDN I can backup only the node I want, by using MyNode.F.Q.D.N (if you get my gist).
If you don’t HAVE the FQDN in the disklist file, then you can’t do that. I’ve also had issues with DLEs that are shorter forms of others, and had to use the “name” (“nickname?) field for those, so I have the control that I want. Deb Baddorf Fermilab > On Jan 2, 2017, at 6:14 PM, Jon LaBadie <[email protected]> wrote: > > In my disklist file I have typically used just the > short name for my hosts rather than the FQDN versions. > I.e. the first line below rather than the second. > > vost Home /home comp-user-tar > vost.jgcomp.com Home /home comp-user-tar > > My server and all the clients are in the same domain > and ip-addr -> hostname queries to my local DNS returns > the short form rather than the FQDN. > > Are there any known places/situations where using the > short hostnames will definitely cause problems? > > The concern arose as I'm still trying to get amdump_client > working. At one point I switched to FQDN to see if that > was a problem but got the surprise error of "no DLEs for > host vost". The amanda server considered the requesting > system to be "vost", not "vost.jgcomp.com". I'm assuming > it picked that up from a DNS query. I see no way to > specify the host on the amdump_client command line. > > Jon > -- > Jon H. LaBadie [email protected] > 11226 South Shore Rd. (703) 787-0688 (H) > Reston, VA 20190 (703) 935-6720 (C)
