Chris/Fleep, Yes, opensim is doing DNS resolution for the remote client.
This is a frequent problem area for implementations with internal and external clients. There's added confusion because using domain names at the client which match those used in the server works to begin login and then fails in the handshake phase. Home networks can often solve the problem by turning on NAT loopback in the router. I agree that split DNS is probably common. Perhaps someone running that environment can offer a suggestion. - Gary Chris/Fleep wrote: On Fri, Apr 1, 2011 at 11:10 AM, Gary Beck <[email protected]> wrote: InternalAddress is the address internally used by the server to listen for traffic - this parameter is not used to inform the client for use in the handshake. To set up the UDP handshake the server resolves the ExternalHostName to an IP address. So if this is correct you're saying that opensim is doing the DNS resolution for the remote client? That seems not good. I mean, surely we're not the only campus with split DNS...
_______________________________________________ Opensim-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-users
