> Currently I do not have a DNS server running. I also do not > have temporary entries in the hosts file of the resloving > machine. Do you have any ideas as to why coldfusion is able > to processes every other template and component on my server > with no problems? (I can access all my pages like: > http://myIP/myCFpage.cfm) I can even consume my handcoded > webservices (w/ http://myIP/whatever.cfc?WSDL) on this > server....as long as the consuming page is also located on > this same server. The problem occurs when I try to consume > that webservice from a template that is on a different > coldfusion server. That is when I get the axis error / > hostname of the server is not being resolved.
Normal HTTP requests and responses don't require reverse name resolution. Apparently, Axis (or SOAP or WSDL) does. > Dave, I am confused as to what all this has to do with DNS or > my DNS server rather? If DNS is simply a pointer to an IP > address, then doesn't that mean a call to my 'readable domain > name' (eg http://www.mysite.com) resolves to my private IP? > For example, when I browse http://www.mysite.com the request > goes out and in the end pulls the information from > http://myIP/index.cfm ? Remember that DNS not only resolves names to IP addresses, but also resolves IP addresses to names - "reverse DNS". > To put it a different way, if this code (that is copied > below) is in a template residing on the same computer as the > webservice, the webservice is able to be invoked and I get no > problems. I get a string returned that says, "Hello there, Jonathan" > > <cfinvoke webservice="http://myIP/webservice?wsdl"; > method="sayHello" > aName="Jonathan" > returnVariable="THE_RESPONSE"> > > However, when I copy this above code and put it on another > coldfusion server (ie http://myIP2 that is located on > different computer than the webservice) I produce the error. Presumably, your localhost can resolve its own name. At least, it can resolve its IP address to the name "localhost". I don't know enough about SOAP and WSDL and the underpinnings of web services to explain why name resolution is required. However, to solve your immediate problem, I would just recommend that you place an entry in the hosts file of your web service client with the future name of the server and its IP address. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ phone: 202-797-5496 fax: 202-797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Purchase from House of Fusion, a Macromedia Authorized Affiliate and support the CF community. http://www.houseoffusion.com/banners/view.cfm?bannerid=35 Message: http://www.houseoffusion.com/lists.cfm/link=i:14:3706 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/14 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:14 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.14 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
