On Thu, 2008-10-09 at 12:41 -0400, Damian Krzeminski wrote: > It's my understanding sipXconfig cannot assume DNS is running since > sipXconfig is supposed to configure DNS...
I can imagine at least 3 scenarios: - DNS is managed externally to sipX - sipX is used to manage DNS (I guess by maintainig zone files which are used by some DNS server) - sipX is used to set up DNS, but after that, DNS is managed externally to sipX > What if sipXconfig had a option "use DNS" and require either IP address > provided or DNS configured? I can easily see sipXconfig looking up the IP address using DNS if the address isn't configured into sipXconfig directly. But we do need to have some way of ensuring that the run-time configuration matches what DNS is handing out. > Finally - trying to prompt some angry responses by asking stupid questions > - why do services need IP address in their configuration. Shouldn't > services use DNS? As Woof says, it's fairly hard to do a good job. Right now, there's one line in config.defs which computes $MY_IP_ADDR, which is copied to all the places where that information is needed. The problem is made worse by the fact that the address is needed in several different situations: Most components need to know the address so their ports are open only for that address. Some config files need the address so they can recognize it as "their" SIP domain. There may be other uses. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
