en-US/Networking.xml

[John J. McDonough]

 en-US/Networking.xml |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit cf5199d41d04b7b59f707cf3e40ec5a7ea9d520c
Author: John J. McDonough <jjmcd at fedoraproject.org>
Date:   Fri Jun 12 14:29:31 2009 -0400

    Correct domain name div.isc.org bug 505607

diff --git a/en-US/Networking.xml b/en-US/Networking.xml
index 33d611e..7a9f61b 100644
--- a/en-US/Networking.xml
+++ b/en-US/Networking.xml
@@ -10,7 +10,7 @@
 			<term>DNSSEC</term>
 			<listitem>
 				<para>
-					The <package>bind</package> and <package>unbound</package> (recursive DNS servers) now enable DNSSEC validation in their default configuration. DNSSEC Lookaside Verification (DLV) is also enabled with the <systemitem class="fqdomainname">dlv.sc.org</systemitem> DLV Registry. This behavior can be modified in <filename>/etc/sysconfig/dnssec</filename> by changing the DNSSEC and DLV settings.
+					The <package>bind</package> and <package>unbound</package> (recursive DNS servers) now enable DNSSEC validation in their default configuration. DNSSEC Lookaside Verification (DLV) is also enabled with the <systemitem class="fqdomainname">dlv.isc.org</systemitem> DLV Registry. This behavior can be modified in <filename>/etc/sysconfig/dnssec</filename> by changing the DNSSEC and DLV settings.
 				</para>
 				<para>
 					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.