I've had this issue in our environment.
We worked around this by substituting the shortname alias with the IP address.
So instead of having alias like this
Server1
Server1.domain1.com
We use this
<IP address of Server1>
Server1.domain1.com
But I fail to see why EMC decided to use this mechanism. I see no benefit with
it only security hole and issues such as this one.
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Joe N. Wallace
Sent: 12. desember 2008 00:05
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] two clients with the same hostname / netbiosname
Jeah its here. Thank you for pointing this out.
http://adsm.org/lists/html/Networker/2005-08/index.html
this is a rather not so nice problem. I took out the shortname for one of
the client yesterday, so the aliases fiels only containes the FQDN.
It does not work. I guess I'll have to start renaming some servers.
2008/12/11 Tim Mooney <Tim.Mooney AT ndsu DOT edu>
> In regard to: Re: [Networker] two clients with the same hostname /...:
>
> hostname resolution is OK.
>>
>> When I define the clients I put the FQDN in the name field. Networker then
>> creates the aliases wichc seems to consist of the FQDN and a shortname.
>>
>> But as Viertel mentions, if I put the FQDN name in the aliases files
>> manually, it does not create a shortname.
>>
>> Now it's just a question if Networker handles that there is no shortname
>> only FQND in the aliases field.
>>
>> I have this issue because now I have two clients with the same hostname,
>> but
>> a different DNS suffix.
>>
>
> We have a lot of this at our site, and I posted about it a few years ago.
> Legato (I think it was before EMC bought them, but don't recall for
> certain) changed the FQDN behavior at 7.1.x and it caused us a lot of
> headaches. See the archives from August of 2005, specifically the thread
> about "7.1.3 client DNS checks".
>
> In addition to the suggestion that Peter made above, we have found it
> useful to have
>
> save -c your.client.fqdn.here
>
> in the "Backup command" for the clients where this is a problem. See
> the thread in the archive for more info.
>
> Tim
> --
> Tim Mooney Tim.Mooney AT ndsu DOT
> edu
> Enterprise Computing & Infrastructure 701-231-1076 (Voice)
> Room 242-J6, IACC Building 701-231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type
> "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
