The maintainer of the netbase package proposed a fundamental change in how network sockets should be managed regarding IPv4 vs. IPv6 (ie. IPv4-mapped IPv6 addresses). He suggested that the default of the net.ipv6.bindv6only kernel variable should be set to 1 (whereas the current default is 0). After "some" discussion (he and two other guys had something to say about the topic in a one and a half month period) he made the change on 6th December 2009.options single-request in /etc/resolv.conf helped me too. Using strace -T ... on the command that exhibits the slow DNS behaviour you can easily identify the culprit.apt-cache policy. In various distributions and APT versions the pinning might behave a bit differently. Checking the output of apt-cache policy (note that there's no package name at the end of the command, thus it'll list your APT sources and their pinning values) reveals most probably the reason why your preferences file does not do whatever you wish it to do.
The installation is pretty much straightforward, no problems at all. It even checks for the availability of the libnspr4 library (and stops if does not find it) and creates the fms user and group for you (however I still suggest to create these manually since you want to have these in the system UID/GID range) and sets up automatic start on boot. The libnspr4 lib can be installed via apt-get install libnspr4-0d, the fms user and group can be created via addgroup --system fms; adduser --system --group fms and for the autostart to work right, you'll have to adjust the start/stop runlevels in /etc/init.d/fms after the installation finished and reset the runlevels of the fms script via update-rc.d fms remove; update-rc.d fms defaults (by default the /etc/init.d/fms script does not include runlevel 2 in the start runlevels and Debian's default runlevel is 2).dhcp3-client package in Debian does not support (yet) the sending of the configured hostname to the DHCP server. Ubuntu has a custom patch that makes this possible (it was added 4 years ago!), but the Debian package maintainer did not feel this to be important enough to add a patch to Debian's package too.
The bugreport on the issue is now 9 years old and a solution for Debian users/admins is still not available (apart from hard coding the hostname into the DHCP client config file of course). It seems that the latest upstream version (>=4.2.0) of the DHCP client already contains support for sending the actual hostname to the DHCP server (btw. 4.2.0 was released in December 2009), but this will get into Debian only with the next major version (the one that'll follow Squeeze, currently codename "Wheezy"). No rush ... we can wait a couple of more years ... maybe a fix'll be available by the time my (future) kids try to install linux on their PC/mobile/watch/whatever. You've got to love Debian's "stableness".
It's either that or you can try your luck with the ever changing (and breaking) Ubuntu. Unfortunately there's nothing in between. Of course one can always turn to a different distro ... RedHat, etc.sysctl to set net.ipv6.conf.all.disable_ipv6 to 1 in case of Squeeze.apt-get update gave me the following error message:W: GPG error: http://oss.oracle.com unstable Release: The following signatures were invalid: KEYEXPIRED 1315142507 KEYEXPIRED 1315142507 KEYEXPIRED 1315142507
W: You may want to run apt-get update to correct these problems
Recent comments
2 days 9 hours ago
2 days 10 hours ago
4 days 15 hours ago
1 week 1 day ago
1 week 2 days ago
1 week 3 days ago
1 week 3 days ago
1 week 3 days ago
1 week 5 days ago
2 weeks 16 hours ago