Lonnie Abelbeck wrote:
Hi,
I want to document this, it might not be a bug per say, but it
might be the root of other problems.
My local DHCP server passes out 2 DNS IP's, the first a local DNS,
the second a public DNS.
$ cat /etc/resolv.conf
search priv.abelbeck.com
nameserver 192.168.100.116
nameserver 68.12.16.25
In my test setup, 68.12.16.25 (backup DNS) is unreachable,
192.168.100.116 is active.
When I start asterisk, it hangs for 90-100 seconds while loading SIP,
then finally continues with the DNS found from the local DNS.
I then swapped my DHCP server entries such that:
$ cat /etc/resolv.conf
search priv.abelbeck.com
nameserver 68.12.16.25
nameserver 192.168.100.116
No change, SIP hangs for 90-100 seconds.
I then made my DHCP server hand out only one address, the active one:
$ cat /etc/resolv.conf
search priv.abelbeck.com
nameserver 192.168.100.116
Fixed, SIP loaded in a second or two.
Now, back to the normal situation:
$ cat /etc/resolv.conf
search priv.abelbeck.com
nameserver 192.168.100.116
nameserver 68.12.16.25
I used 'ping' to resolve names, and things resolved quickly, not
matter that 68.12.16.25 was unreachable. Therefore this is an
asterisk DNS thing. I'm hoping this behavior might direct the focus
of other problems.
Clearly, one secondary and unreachable DNS server should not halt
asterisk for 90-100 seconds.
Lonnie
Lonnie,
Asterisk is known to have some DNS problems. I don't think that it
is AstLinux specific. Could you try sending this to Asterisk-users?
--
Kristian Kielhofner
___
Astlinux-users mailing list
Astlinux-users@lists.kriscompanies.com
http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL
PROTECTED]
