Your message dated Tue, 27 Feb 2007 21:38:51 -0500
with message-id <[EMAIL PROTECTED]>
and subject line verisign being relevant so last hemi-decade..
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: dnsmasq
Version: 1.15-1
Severity: wishlist
The problem with hardcoding verisign's IP address is that it may change.
It's fine as a quick hack in reaction to the verisign mess, but ISC's
approach in bind9 is much cleaner, as it does not matter if the IP
address changes. I hope dnsmasq can support the same technique; this
would make it much easier to ship dnsmasq with verisign wildcarding
disabled by default and hope that it might still work half a year down
the road.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux dragon 2.4.22 #1 Tue Aug 26 17:27:18 EDT 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages dnsmasq depends on:
ii libc6 2.3.2-4 GNU C Library: Shared libraries an
ii netbase 4.13 Basic TCP/IP networking system
-- no debconf information
--
see shy jo
pgpz0D8yfsNAk.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
--
see shy jo
signature.asc
Description: Digital signature
--- End Message ---
