On Thu, 2008-10-09 at 10:16 -0400, Dale Worley wrote: > On Thu, 2008-10-09 at 09:20 -0400, Damian Krzeminski wrote: > > I do not think it's an ideal solution, but it seemed to me that asking > > admin to enter IP address of the server was the only option. We cannot run > > DNS query since sipXconfig data is going to be used to generate DNS > > configuration. All we could do is to add configuration tests that would > > verify if what we know about DNS names and IP addresses still reflects the > > reality. > > I would expect that the user already has DNS running, and that it > translates the host name into an IP address. Although I might be wrong > about that...
Alas, often not true and we'll have to provide the DNS service. > I think the bigger problem would be if the host name was > multi-homed; how do you choose the right address? First - at present we don't really support multi-homed systems. The get_def_addr script (which I _really_ want to get rid of in this release) does not always do the right thing in this and in other cases. Also, we have some services that still bind to multiple interfaces when they should not (there's an issue on that). The main reason we don't support multi-homed systems well is that the stack does a poor job - it hard-codes putting an address into the Via. So let's say that we have a host on the 10.x net and the 47.x net - if everything that might get the Via on either network knows how to route to any address on either network, everything would work, but in most multi-homed situations the whole point is that they don't. So... services need exactly one address that the human has chosen so that it will work. The best way to get it is, alas, to ask the human. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
