Linux ns8.secondary29.go.th 2.6.32-754.28.1.el6.x86_64 #1 SMP Wed Mar 11 18:38:45 UTC 2020 x86_64
Apache/2.2.15 (CentOS)
: 122.154.134.11 | : 122.154.134.9
Cant Read [ /etc/named.conf ]
5.6.40
apache
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
bind-9.8.2 /
misc /
[ HOME SHELL ]
Name
Size
Permission
Action
Makefile
12.4
KB
-rw-r--r--
Makefile.in
1.63
KB
-rw-r--r--
dnssec
3.02
KB
-rw-r--r--
format-options.pl
1.47
KB
-rw-r--r--
ipv6
4.44
KB
-rw-r--r--
migration
11.07
KB
-rw-r--r--
migration-4to9
2.01
KB
-rw-r--r--
options
26.74
KB
-rw-r--r--
rfc-compliance
1.66
KB
-rw-r--r--
roadmap
1.99
KB
-rw-r--r--
sdb
6.4
KB
-rw-r--r--
sort-options.pl
1.35
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : rfc-compliance
Copyright (C) 2004 Internet Systems Consortium, Inc. ("ISC") Copyright (C) 2001 Internet Software Consortium. See COPYRIGHT in the source root or http://isc.org/copyright.html for terms. $Id: rfc-compliance,v 1.4 2004-03-05 05:04:53 marka Exp $ BIND 9 is striving for strict compliance with IETF standards. We believe this release of BIND 9 complies with the following RFCs, with the caveats and exceptions listed in the numbered notes below. Note that a number of these RFCs do not have the status of Internet standards but are proposed or draft standards, experimental RFCs, or Best Current Practice (BCP) documents. RFC1034 RFC1035 [1] [2] RFC1123 RFC1183 RFC1535 RFC1536 RFC1706 RFC1712 RFC1750 RFC1876 RFC1982 RFC1995 RFC1996 RFC2136 RFC2163 RFC2181 RFC2230 RFC2308 RFC2535 [3] [4] RFC2536 RFC2537 RFC2538 RFC2539 RFC2671 RFC2672 RFC2673 RFC2782 RFC2915 RFC2930 RFC2931 [5] RFC3007 [1] Queries to zones that have failed to load return SERVFAIL rather than a non-authoritative response. This is considered a feature. [2] CLASS ANY queries are not supported. This is considered a feature. [3] Wildcard records are not supported in DNSSEC secure zones. [4] Servers authoritative for secure zones being resolved by BIND 9 must support EDNS0 (RFC2671), and must return all relevant SIGs and NXTs in responses rather than relying on the resolving server to perform separate queries for missing SIGs and NXTs. [5] When receiving a query signed with a SIG(0), the server will only be able to verify the signature if it has the key in its local authoritative data; it will not do recursion or validation to retrieve unknown keys.
Close
