Tim,
Ouch.. we just completed some major 6.1.3 to 7.1.1 upgrades and the
new DNS lookup feature was a major roadblock.
We did not have such a dire problem as you do though; we did not have
a setup with hostA.domain1 and hostA.domain2 where the short name
hostA would conflict. We simply made sure for each client all its
interfaces resolved in DNS and the names were all present in the alias
list. Even after that we found Networker doing DNS lookups and not
getting what it wanted; corrections to DNS sometimes helped.
If you can do the save -c hostA.domain1 workaround that would be
a start. I don't quite understand how this can fix everything though;
we found Networker wanting to resolve other client interfaces sometimes.
If you have 2 clients with many interfaces in common will a save -c
clientnameA.domain1 fix conflicts for all short names?
Good luck.
Robert Maiello
Pioneer Data Systems.
On Sat, 20 Aug 2005 20:26:00 -0500, Tim Mooney
<mooney AT DOGBERT.CC.NDSU.NODAK DOT EDU> wrote:
>All-
>
>Because of the recent security vulnerability and because there are not
>patched clients (and apparently won't be) for 6.1.x, I've updated a large
>number of our backup clients to the 7.1.3 Build 421 client this weekend.
>In doing so, I've encountered a problem with the DNS checks in the 7.1.3
>client, and I'm not sure how to mollify the new client. I'm hoping
>someone on the list has some suggestions.
>
>There are a few bits of important background information:
>
>- we use mixed case in our DNS domain name.
>
>- our backup server and our largest backup clients are on two networks:
> our primary network and a backup-only network. If a hostname on the
> primary network is foo.NoDak.edu, then its interface on our backup
> network is foo-2.NoDak.edu.
>
>- The clients are created within NetWorker using the fully qualified
> domain name of the interface on the backup network, e.g. foo-2.nodak.edu.
> In all cases, I've also added an alias in the client definition for
> the fully qualified domain name of the public interface, e.g.
> foo.nodak.edu.
>
> Note, though, that the clients were all created and the aliases were all
> added without using mixed case in the name.
>
>- The `hostname' command on each of the clients returns the fully
> qualified domain name (with mixed case) of the primary interface. In
> all cases, the /etc/hosts file has the correct entry for the primary
> interface:
>
> XXX.YYY.ZZZ.AAA foo.NoDak.edu foo
>
>
> Many of our clients don't have an /etc/hosts entry for their secondary
> (backup) interface's hostname.
>
>- Lastly, we have a few clients with the same "short name" in different
> subdomains, e.g. foo.subnet1.NoDak.edu (which is created within
> NetWorker as foo-2.subnet1.nodak.edu), foo.subnet2.NoDak.edu (in
> NetWorker it's foo-2.subnet2.nodak.edu), etc. In all cases, those
> clients are using their fully qualified domain name of their
> primary/public interface as their hostname.
>
>
>
>DNS resolution is set up, and is working correctly. Everything worked
>perfectly with the 6.1.x client.
>
>After upgrading the clients to the 7.1.3.421 backup client, though, backups
>now fail with the "...is not properly configured" error message. Here's
>an example for one of our IMAP servers:
>
>* imap1-2.ndsu.nodak.edu:/ save: SYSTEM error: client `imap1' is not
properly configured on the NetWorker Server
>* imap1-2.ndsu.nodak.edu:/ or `imap1' is not in the aliases list for
>* client `imap1-2.ndsu.nodak.edu'
>
>
>
>The crux of the problem seems to be that NetWorker is for some reason
>wanting the short name `imap1' to be in the aliases list for this client.
>I don't see why; the client machine is using its fully qualified domain
>name:
>
>$hostname
>imap1.ndsu.NoDak.edu
>
>
>I can't add just `imap1' to the aliases list for this client, because then
>NetWorker gets this client confused with other clients in other subdomains
>that also have short names of `imap1' (even though all of those clients
>are also using their fully qualified domain name). For example, we also
>have backup clients name
>
> imap1-2.nodak.edu
> imap1-2.sendit.nodak.edu
>
>Those clients are also both correctly using their fully qualified domain
>names as their hostname, e.g. imap1.NoDak.edu and imap1.sendit.NoDak.edu.
>
>I'm not sure how to proceed. It looks to me like NetWorker is doing
>the wrong thing (truncating what the client returns as its hostname) and
>requiring that short name to be on the aliases list. That makes it
>impossible to have two clients with the same short name (even if they're
>not using the short name as their hostname) in different subdomains.
>
>Anyone have any suggestions or ideas for how to work around this?
>
>Tim
>--
>Tim Mooney mooney AT dogbert.cc.ndsu.NoDak DOT edu
>Information Technology Services (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
>wit 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
wit 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
|
