One of the reasons that STAF resolves hostnames is because if you're using
dynamic DNS (DDNS), the IP address can dynamically change. For example,
if a long running STAF PROCESS START request is submitted with a NOTIFY
option, when the process completes on the remote system it sends a
STAF/Process/Complete message to the hostname of the system that submitted
the PROCESS START request. If the IP address of the system that submitted
the request has been changed while the process was running on the remote
system (e.g. due to DDNS), then the STAF/Process/Complete message would be
sent to the wrong IP if STAF didn't resolve the hostname and the
submitting system would never be notified that the process completed.
There isn't currently a way to disable STAF from looking up hostnames. You
need to fix your hostname resolution issues.
We have an open STAF feature #1346181: "Add Option to make STAF _NOT_
lookup hostnames" at
https://sourceforge.net/tracker/?func=detail&aid=1346181&group_id=33142&atid=407384
that will add an option to not perform hostname lookups. Please add a
comment to this feature stating why you would like it. This feature has
been requested by several people so it is a higher priority feature that
hopefully it will be implemented soon.
--------------------------------------------------------------
Sharon Lucas
IBM Austin, luc...@us.ibm.com
(512) 286-7313 or Tieline 363-7313
From: Josh <smy...@gmail.com>
To: staf-users@lists.sourceforge.net,
Date: 06/13/2012 04:09 PM
Subject: [staf-users] STAF Hostname Issues
Hi,
I've read through the documentation a few times to try and find a section
that covers this, but I could not find it..
Why does the return message of a STAF command try and resolve the hostname
of the machine issuing the command? Why does the remote STAF just not use
the IP of the machine that originated the command? Is there any way to
force it to use IP addresses instead of trying to resolve hostnames?
The way I see it working right now..
MachineA (192.168.1.100) -> STAF Command -> MachineB (192.168.1.101)
1) MachineB completes command
2) MachineB tries to resolve the hostname "MachineA" to resend the
response back
---
One of my commands is intermittently successful which is very frustrating
and I suspect it has something to do with hostname resolution problems.
The command executes successfully on the remote host but never reports
back that it was successful.
Thanks,
Josh
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
