Page History

All linux servers use IPv6 resolvers

Only statically configured IPv6 addresses in /etc/resolv.conf

All linux managed by SSH on IPv6 only

Configure ListenAddress :: in sshd_config.

All linux servers run Postfix on IPv6 only (except public mail server)

Remove IPv4 address from $mynetworks, and set inet_protocols = ipv6

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="1ebb484921fb2925-a177d93f-406a447c-9b9ab031-018d02496c5b5396b70fc054"><ac:plain-text-body><![CDATA[

Nagios runs only on IPv6

Configure Listen [2001:610:158:98d::42]:80 in /etc/apache/ports.conf.

]]></ac:plain-text-body></ac:structured-macro>

Entire host IPv6 (removed IPv4 address and A record)

svn.terena.org

WinSCP

Upgrade to 4.2.8 or later to get IPv6 going

EMS PostgresQL manager

Tunneling via SSH does not work. Native Postgres connections work, so the bug must be in sshfwd.dll.

TurtoiseSVN

I had some repositories checked out with TurtoiseSVN, using my SSH keys from Putty/Pageant. Any actions on the repository started to have a really long delay after switching off IPv4 on the subversion server. Fixed after using the right repository URL format, in my case using the Putty session name instead of the host name. This session has everything set properly already. In my case the hostname is svn.terena.org, and the PuTTY session name is svn.

Remote Desktop client (mstsc.exe)

A RDP (Remote Desktop) connection to a Windows 7 computer using a hostname that only has a AAAA record takes 11 seconds. mstsc.exe does an A query first, gets back a No such name, then wait 11 seconds, then asks for and receives the AAAA record, and then immediately connects.