One thing that worked for me was to add an entry to the hosts file (assuming
you use that) which lists the sl0 interface that diald uses to detect traffic.
In my case I used a local and remote pair in diald.conf ;
local 192.168.2.10
remote192.168.2.20
so I added the local address to the hosts file;
# bogus interface to keep named happy with diald
192.168.2.10 bogus.localdomain bogus
Also, to host.conf I added;
# use hosts file before using nameserver lookups
order hosts bind
That stopped named from trying to call a nameserver for a lookup for that diald
address (reverse lookup?) and eliminated a lot of connect attempts (once every
15 minutes or so). What I do not know (yet) is if this causes any other
problems. It all appeared t owork OK. Perhaps someone can comment??
alex
On Tue, 12 Oct 1999, Vikash wrote:
> Hello,
>
> I am having trouble in keeping diald under control when named is running.
>
> The link keeps coming up or stays up.
>
> Has anyone managed to keep them both happy?
>
> Please let me know.
>
> Thanks in advance.
>
> Regards,
> Vikash.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
