** Slight correction ** - Should read: "works for me with multiple domain names pointing at the single public IP of the server". Though would probably work with multiple public IPs too as long as you "listen" on the local IP and do an internal translation (on your network) of the public IPs to all point at the same local IP of the server. But that's a whole other story...

On 11/7/06, Max Gregorian <gregorian442@googlemail.com> wrote:
Which is the actual domain name that the server is supposed to be responsible for? sipserver.mobilia.it or just mobilia.it or both?
 
 
sipserver.mobilia.it seems to be fine:
 
Domain Type Class TTL Answer
sipserver.mobilia.it. A IN 86400 89.202.252.16
mobilia.it. NS IN 86400 dns2.nic.it.
mobilia.it. NS IN 86400 sipserver.mobilia.it.
mobilia.it. NS IN 86400 ns.mobilia.it.
ns.mobilia.it. A IN 86400 151.17.2.2

 
Are you after a multi-domain setup? As I understand it the domain module (if that is what your are using) is meant to be good for multi-domain setups, but have you considered keeping it simple and testing with a simple setup initially?
 
Just do:
 
listen=udp:89.202.252.16:5060       # IP address of Server #
listen=udp: sipserver.mobilia.it:5060 # Domain of server #
I think you will need these, regardless of whether you are using the domain module or not. And then I just use:
 
if (!uri==myself) {
}
 
It certainly works for me, even in a multi-domain setup with multiple public IPs, if not a little unwieldy.