| /freebsd/contrib/unbound/dnstap/ |
| H A D | dnstap.proto | 1 // dnstap: flexible, structured event replication format for DNS software
4 // replication format for DNS software.
25 // DNS server identity.
26 // If enabled, this is the identity string of the DNS server which generated
31 // DNS server version.
32 // If enabled, this is the version string of the DNS server which generated
59 // SocketProtocol: the protocol used to transport a DNS message.
61 UDP = 1; // DNS over UDP transport (RFC 1035 section 4.2.1)
62 TCP = 2; // DNS over TCP transport (RFC 1035 section 4.2.2)
63 DOT = 3; // DNS over TLS (RFC 7858)
[all …]
|
| /freebsd/crypto/openssh/ |
| H A D | README.dns | 1 How to verify host keys using OpenSSH and DNS
4 OpenSSH contains support for verifying host keys using DNS as described
6 instructions on how to use this feature. Configuring DNS is out of the
10 (1) Server: Generate and publish the DNS RR
12 To create a DNS resource record (RR) containing a fingerprint of the
22 generic DNS RR format parsable by most modern name server
26 To publish the fingerprint using the DNS you must add the generated RR
27 to your DNS zone file and sign your zone.
30 (2) Client: Enable ssh to verify host keys using DNS
32 To enable the ssh client to verify host keys using DNS, you have to
[all …]
|
| /freebsd/crypto/openssl/test/recipes/80-test_cmp_http_data/Mock/ |
| H A D | test.cnf | 129 DNS.0 = localhost
138 DNS.0 = localhost
139 DNS.1 = xn--rksmrgs-5wao1o.example.com
140 DNS.2 = xn--rkmacka-5wa.example.com
|
| /freebsd/libexec/bootpd/ |
| H A D | Problems | 21 timeouts on failed DNS lookup operations. If this is the
22 problem, find the client names for which DNS lookup fails
31 If your DNS lookups work but are just slow, consider either
32 running bootpd on the same machine as the DNS server or
33 running a caching DNS server on the host running bootpd.
|
| /freebsd/crypto/heimdal/lib/wind/ |
| H A D | rfc3490.txt | 40 required in existing protocols like DNS, so that IDNs can be
54 3.2.1. DNS resource records................................ 8
68 6. Implications for typical applications using DNS............... 13
71 6.3 DNS servers............................................... 15
90 does not depend on any changes to DNS servers, resolvers, or protocol
91 elements, because the ASCII name service provided by the existing DNS
106 and DNS servers being updated in order for a user to use an
109 applications only; no changes are needed to the DNS protocol or any
110 DNS servers or the resolvers on user's computers.
125 IDNA does not extend the service offered by DNS to the applications.
[all …]
|
| /freebsd/contrib/openresolv/ |
| H A D | resolvconf.in | 85 Inform the system about any DNS updates.
88 -a \$INTERFACE Add DNS information to the specified interface
89 (DNS supplied via stdin in resolv.conf format)
90 -d \$INTERFACE Delete DNS information from the specified interface
92 -i [\$PATTERN] Show interfaces that have supplied DNS information
95 -l [\$PATTERN] Show DNS information, optionally from interfaces
98 -u Run updates from our current DNS information
103 -m metric Give the added DNS information a metric
|
| /freebsd/contrib/unbound/doc/ |
| H A D | FEATURES | 27 RFC 1123, 6.1 Requirements for DNS of internet hosts.
41 RFC 4697: No DNS Resolution Misbehavior.
42 RFC 5001: DNS Name Server Identifier (NSID) Option
46 service. In fact for all DNS service so cache snooping is halted.
68 This is not a DNS statistics package, but some operationally useful
|
| H A D | README.tests | 11 * dig - from the bind-tools package. Used to send DNS queries.
14 * ldns-testns - from ldns examples. Used as DNS auth server.
|
| H A D | requirements.txt | 14 This is the requirements document for a DNS name server and aims to
15 document the goals and non-goals of the project. The DNS (the Domain
19 Data in the DNS is stored in Resource Record sets (RR sets), and has a
22 looks up data in the DNS for clients and caches previous answers to
26 that also DNSSEC (secure DNS) validation and stub-resolvers (that do not
31 hierarchical DNS servers that own the data and the Cache that stores
55 o A validating recursive DNS resolver.
56 o Code diversity in the DNS resolver monoculture.
239 reassurance that the DNS server does EDNS does not mean that path can
240 take large DNS answers.
|
| /freebsd/contrib/sendmail/cf/mailer/ |
| H A D | smtp.m4 | 111 …P_MAILER_MAXRCPTS', `r=', `, ')_OPTINS(`SMTP_MAILER_CHARSET', `C=', `, ')T=DNS/RFC822/SMTP,_SMTP_Q…
114 …P_MAILER_MAXRCPTS', `r=', `, ')_OPTINS(`SMTP_MAILER_CHARSET', `C=', `, ')T=DNS/RFC822/SMTP,_ESMTP_…
117 …P_MAILER_MAXRCPTS', `r=', `, ')_OPTINS(`SMTP_MAILER_CHARSET', `C=', `, ')T=DNS/RFC822/SMTP,_SMTP8_…
120 …P_MAILER_MAXRCPTS', `r=', `, ')_OPTINS(`SMTP_MAILER_CHARSET', `C=', `, ')T=DNS/RFC822/SMTP,_DSMTP_…
123 …Y_MAILER_MAXMSGS', `m=', `, ')_OPTINS(`SMTP_MAILER_MAXRCPTS', `r=', `, ')T=DNS/RFC822/SMTP,_RELAY_…
|
| /freebsd/sbin/natd/samples/ |
| H A D | natd.cf.sample | 56 # BEFORE running named, so if the DNS server and NAT are on the same
76 # DNS in this situation can get hairy. For example, an inside host
79 # 192.168.1.56 and 198.105.232.1 are set up as address records in the DNS
88 # It's probably not a good idea to use DNS names in redirect_address statements
|
| /freebsd/usr.sbin/bsdconfig/networking/include/ |
| H A D | messages.subr | 45 msg_dns_configuration="DNS Nameserver Configuration:\nChoose Exit when finished else Cancel."
46 msg_dns_nameservers="DNS nameservers"
83 msg_please_enter_nameserver="Please enter the new IP address of the DNS nameserver:"
84 msg_please_enter_nameserver_existing="Please enter the new IP address of the DNS nameserver\n(set t…
88 msg_removing_nameserver="Removing DNS nameserver from resolv.conf(5)..."
95 msg_saving_nameserver="Saving new DNS nameserver to resolv.conf(5)..."
96 msg_saving_nameserver_existing="Editing DNS nameserver in resolv.conf(5)..."
105 xmsg_please_enter_nameserver_existing="Please enter the new IP address of the DNS nameserver\n(set …
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | X509_check_host.pod | 65 addresses stored in DNS names and Common Names are ignored. There are
92 one subject alternative name of the right type (DNS name or email
98 names of the right type (DNS name or email address as appropriate); the default
113 constitutes the complete label of a DNS name (e.g. "*.example.com")
121 would match a peer certificate with a DNS name of "www.example.com",
122 but would not match a peer certificate with a DNS name of
|
| /freebsd/contrib/ntp/scripts/update-leap/ |
| H A D | update-leap-opts.def | 28 descrip = "Use only IPv4 addresses for DNS name resolution";
30 Force DNS resolution of following host names on the command line
39 descrip = "Use only IPv6 addresses for DNS name resolution";
41 Force DNS resolution of following host names on the command line
|
| /freebsd/secure/caroot/untrusted/ |
| H A D | Hellenic_Academic_and_Research_Institutions_RootCA_2011.pem | 56 DNS:.gr
57 DNS:.eu
58 DNS:.edu
59 DNS:.org
|
| /freebsd/contrib/unbound/contrib/ |
| H A D | unbound_cache.cmd | 3 rem -- DNS cache save/load script
95 echo l - Load - default mode. Warming up Unbound DNS cache from saved file. cache-ttl must be high …
96 echo s - Save - save Unbound DNS cache contents to plain file with domain names.
|
| H A D | unbound.spec | 1 Summary: Validating, recursive, and caching DNS resolver
14 Unbound is a validating, recursive, and caching DNS resolver.
21 DNSSEC (secure DNS) validation and stub-resolvers (that do not run
|
| /freebsd/contrib/sendmail/cf/feature/ |
| H A D | dnsbl.m4 | 20 # map for DNS based blocklist lookups
27 # DNS based IP address spam list _DNSBL_SRV_
|
| H A D | enhdnsbl.m4 | 19 # map for enhanced DNS based blocklist lookups
35 # DNS based IP address spam list _EDNSBL_SRV_
|
| /freebsd/usr.sbin/bsdconfig/share/media/ |
| H A D | http.subr | 265 # ^^^ IPv6 above / DNS Name or IPv4 below vvv
267 *:*/*) # DNS name or IPv4 address with port and directory
269 "DNS name or IPv4 addr" "$hostname"
275 *:*) # DNS name or IPv4 address with port
276 f_dprintf "Looks like a DNS name or IPv4 addr with port: %s" \
281 */*) # DNS name or IPv4 address with directory
282 f_dprintf "Looks like a DNS name or IPv4 addr with dir: %s" \
287 *) # DNS name or IPv4 address
288 f_dprintf "Looks like a DNS name or IPv4 addr: %s" "$hostname"
314 f_dprintf "Found DNS entry for %s successfully." "$hostname"
[all …]
|
| /freebsd/crypto/heimdal/doc/ |
| H A D | kerberos4.texi | 49 Using DNS for this is tempting, but DNS is error prone, slow and unsafe
50 @footnote{at least until secure DNS is commonly available}.
73 principals. For instance, if you are using DNS lookups and you have two
150 Instead of doing this you can use DNS to convert instances. This is not
154 To enable DNS lookup you should turn on @samp{v4_instance_resolve} in
|
| /freebsd/contrib/unbound/smallapp/ |
| H A D | unbound-control-setup.sh.in | 139 subjectAltName=DNS:$SERVERNAME
175 subjectAltName=DNS:$CLIENTNAME
|
| /freebsd/contrib/ntp/sntp/ |
| H A D | sntp-opts.def | 26 descrip = "Force IPv4 DNS name resolution";
28 Force DNS resolution of the following host names on the command line
37 descrip = "Force IPv6 DNS name resolution";
39 Force DNS resolution of the following host names on the command line
84 as part of a DNS lookup are assumed to be for a single instance of
89 returned for the DNS lookup of the supplied host-name are on
|
| /freebsd/lib/libwrap/ |
| H A D | hosts.allow | 28 # Protect against simple DNS spoofing attacks by checking that the
31 # 20 seconds is logged. No protection is afforded against DNS poisoning,
32 # IP spoofing or more complicated attacks. Hosts with no reverse DNS
|
| /freebsd/contrib/netbsd-tests/ipf/input/ |
| H A D | ni13 | 185 … S:6 A:7 ppp: IPCP 36: Conf-Req(5), IP-Addr=0.0.0.0, Pri-DNS=0.0.0.0, Pri-NBNS=0.0.0.0, Sec-DNS=0.…
193 …e [KSAv1] ID:4000 S:8 A:6 ppp: IPCP 30: Conf-Rej(5), Pri-DNS=0.0.0.0, Pri-NBNS=0.0.0.0, Sec-DNS=0.…
|