Documentation Networking Beat

Networking

This section contains information about networking changes in Fedora 11.

DNSSEC

The bind and unbound recursive DNS servers now enable DNSSEC validation in their default configuration. DNSSEC Lookaside Verification (DLV) is also enabled with the dlv.sc.org DLV Registry. This behavior can be modified in /etc/sysconfig/dnssec by changing the DNSSEC and DLV settings.

With DNSSEC enabled, when a domain supplies DNSSEC data (such as .gov, .se, the ENUM zone and other TLD's) then that data will be cryptographically validated on the recursive DNS server. If validation fails due to attempts at cache poisoning, for example via a Kaminsky Attack, then the end user will not be given this forged/spoofed data. DNSSEC deployment is gaining speed rapidly, and is a crucial and logical step to make the Internet more secure for end users. DLV is used to add DNSSEC signed domains into TLD's that themselves are not yet signed, such as .com and .org.

TigerVNC

TigerVNC is used as default VNC project. Package names were changed to tigervnc, tigervnc-server and tigervnc-server-module. Binary names are the same as in previous versions. The libvnc.so module has been moved to the tigervnc-server-module subpackage. Otherwise there should be no difference.

Ethernet connections are not started at first boot

See Template:Rhbug. If you install Fedora 11 using a non-network-based method (e.g. CD or DVD), ethernet connections will not be automatically initialized at first boot, which is not the behaviour most people would expect. This is in fact intentional (enabling network interfaces on boot by default has security implications in some situations), but in future Fedora releases, there will be an option in the installer to designate which interfaces should be started at boot time. For this release, simply use the NetworkManager tray icon to enable the ethernet interface you wish to use.