On Wed, Aug 20, 2008 at 12:11 PM, Andrew Robert Gordon Henry Naylor < [EMAIL PROTECTED]> wrote:
> Thats the problem though, if I put in my DNS address then it didn't bind to > the address correctly. It can only be one or the other. By the sounds of it, > both a <bind address> field is needed and a <host> field, that would have > seemed like the sensible thing to do in the first place. > Odd, because that's how I run it. Ahhhh, it binds to my internal IP address, but I have NAT'ing enabled, so the connections magically work. (My transport runs on the box that does the NAT'ing) Still I would expect it to work in a split dns configuration, i.e. the dns name needs to resolve to the internal IP address when the transport or internal machines resolve it, and to the public IP address when machines outside your network resolve it. -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "py-transports" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/py-transports?hl=en -~----------~----~----~----~------~----~------~--~---
