reassign 314616 no-ip
thanks
Glibc's standard behaviour is to cache the contents of /etc/resolv.conf
across multiple calls to gethostbyname(). I doubt this will change any
time soon.
The solution to this bug is probably for no-ip to call res_init() prior
to attempting resolution, if it suspects
Package: no-ip
Severity: normal
Hi,
I have my dsl router attached to a sarge box with no-ip running, however it can
happen that eth0 goes up with the wrong nameserver in resolv.conf, then the
router renews the ip with dhcp and nameserver is correctly setted. no-ip daemon
doesn't like this and it k
2 matches
Mail list logo
