Package: ez-ipupdate Version: 3.0.11b8-8 Severity: important
Hello, Looks like ez-ipupdate use a cache file to detect an IP difference, the test will eventually fail if the IP got changed by another service (for example when you multi boot with another operating system). My debian box is always assigned IP_A. When I reboot under Windows the box is assigned IP_B, so the dyndns entry is now pointing to IP_B. Going back to debian, box is assigned IP_A, ez-ipupdate look at the cache file and see that the last change was IP_A so it accordingly does not change anything. Still the dyndns.org entry point to IP_B wich is not correct. When the daemon use caching, it should probably test if the dns entry is correct with "host hostname.domain". Just to be sure the cached data is accurate. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-k7 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages ez-ipupdate depends on: ii adduser 3.59 Add and remove users and groups ii debconf [debconf-2.0] 1.4.30.11 Debian configuration management sy ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an -- debconf information: * ez-ipupdate/dns_mx: twenkill.dyndns.org * ez-ipupdate/service_type: dyndns * ez-ipupdate/username: thoane * ez-ipupdate/daemon: true ez-ipupdate/server: * ez-ipupdate/dns_wildcard: false * ez-ipupdate/manage_default_config_automatically: true * ez-ipupdate/hostname: twenkill.dyndns.org * ez-ipupdate/interface: eth0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
