ADSM-L

[ADSM-L] Changing DNS name of node - made server mad

2010-04-06 16:03:20
Subject: [ADSM-L] Changing DNS name of node - made server mad
From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 6 Apr 2010 16:02:45 -0400
We discovered that a new client node was getting an incorrect DNS name
resolution, from the TSM server, due to someone reassigning the IP but not
removing the DNS entry and the TSM server doing reverse-lookups.

So we removed the DNS entry, thus making the TSM server mad (see errors
below).  It spewed out hundreds of the "Unable to resolve address"
messages.  This box does not have nor need a DNS entry.

4/6/2010 4:11:06 AM ANR8218W Unable to resolve address for
team.ucc.vcu.edu.
4/6/2010 4:11:36 AM ANR8218W Unable to resolve address for
team.ucc.vcu.edu.
4/6/2010 4:12:06 AM ANR8218W Unable to resolve address for
team.ucc.vcu.edu.
4/6/2010 4:12:36 AM ANR8218W Unable to resolve address for
team.ucc.vcu.edu.
4/6/2010 4:13:06 AM ANR8218W Unable to resolve address for
team.ucc.vcu.edu.
4/6/2010 4:13:36 AM ANR8218W Unable to resolve address for
team.ucc.vcu.edu.
4/6/2010 4:14:02 AM ANR2578W Schedule RO in domain RADONC for node RO-CVS
has missed its scheduled start up window.


My question is, do I need to do anything about this or will the TSM server
just "get over it"?
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html

<Prev in Thread] Current Thread [Next in Thread>