This is a known bug in NSStream which we've fixed, but the fix is not
available in an SU. If this is affecting you, please let us know ASAP
with details as to the impact it has to your application.
.chris
--
Chris Parker
Cocoa Frameworks
Apple Computer, Inc.
On Aug 21, 2005, at 2:33 PM, Samuel Tesla wrote:
Hello,
I posted back in June about what seems to be a bug in either
NSStream or NSHost. This bug shows up when you attempt to connect
to a host specified by IP address when the reverse DNS lookup
returns a hostname that does not resolve.
I've attached the source to the test program I wrote to test this
out, and you can see the log below of the results.
I haven't been able to find any programmatic solutions to this
problem. The best I can do is add a hostname to my /etc/hosts file
that resolves to the IP.
I ran across a very interesting problem with NSStream.
When I create an NSHost object, it appears to do its best to fill
both the address and the names out. If I create it using and IP,
it will do reverse DNS lookups. The interesting problem comes up
when I create an NSHost from an IP address, but the hostname that
reverse DNS finds is not a good one. In that case it gets errors
when it tries to get the streams.
I've attached the program I used to generate the following output.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macnetworkprog/email@hidden
This email sent to email@hidden
