Home
last modified time | relevance | path

Searched refs:DNS (Results 1 – 25 of 161) sorted by relevance

1234567

/NextBSD/contrib/unbound/dnstap/
HDdnstap.proto1 // dnstap: flexible, structured event replication format for DNS software
4 // replication format for DNS software.
24 // DNS server identity.
25 // If enabled, this is the identity string of the DNS server which generated
30 // DNS server version.
31 // If enabled, this is the version string of the DNS server which generated
65 // Message: a wire-format (RFC 1035 section 4) DNS message and associated
97 // "forwarding" case where an upstream DNS server is responsible for
107 // AUTH_QUERY is a DNS query message received from a resolver by an
112 // AUTH_RESPONSE is a DNS response message sent from an authoritative
[all …]
/NextBSD/crypto/openssh/
HDREADME.dns1 How to verify host keys using OpenSSH and DNS
4 OpenSSH contains support for verifying host keys using DNS as described in
6 on how to use this feature. Configuring DNS is out of the scope of this
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 …]
/NextBSD/contrib/unbound/libunbound/python/doc/examples/
HDexample1b.rst4 Reverse DNS lookup
7 Reverse DNS lookup involves determining the hostname associated with a given IP address.
10 For the reverse DNS records, the special domain in-addr.arpa is reserved.
11 For example, a host name for the IP address 74.125.43.147 can be obtained by issuing a DNS query fo…
/NextBSD/contrib/unbound/libunbound/python/doc/
HDintro.rst6 `Unbound`_ is an implementation of a DNS resolver, that performs caching and DNSSEC validation.
37 * DNS-based applications performing DNS lookups; the caching resolver can reduce overhead
38 * Applications where the validation of DNS records is required
39 …* Great solution for customizable and dynamic DNS-based white/blacklists (spam rejection, connecti…
/NextBSD/usr.sbin/pc-sysinstall/backend-query/
HDenable-net.sh45 DNS="$4"
96 if [ -n "${DNS}" ]; then
97 echo "nameserver ${DNS}" >>/etc/resolv.conf
/NextBSD/contrib/openresolv/
HDresolvconf.in76 Inform the system about any DNS updates.
79 -a \$INTERFACE Add DNS information to the specified interface
80 (DNS supplied via stdin in resolv.conf format)
81 -m metric Give the added DNS information a metric
84 -d \$INTERFACE Delete DNS information from the specified interface
87 -u Run updates from our current DNS information
88 -l [\$PATTERN] Show DNS information, optionally from interfaces
90 -i [\$PATTERN] Show interfaces that have supplied DNS information
/NextBSD/crypto/heimdal/lib/wind/
HDrfc3490.txt40 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 …]
/NextBSD/libexec/bootpd/
HDProblems22 timeouts on failed DNS lookup operations. If this is the
23 problem, find the client names for which DNS lookup fails
32 If your DNS lookups work but are just slow, consider either
33 running bootpd on the same machine as the DNS server or
34 running a caching DNS server on the host running bootpd.
/NextBSD/sbin/natd/samples/
HDnatd.cf.sample57 # BEFORE running named, so if the DNS server and NAT are on the same
77 # DNS in this situation can get hairy. For example, an inside host
80 # 192.168.1.56 and 198.105.232.1 are set up as address records in the DNS
89 # It's probably not a good idea to use DNS names in redirect_address statements
/NextBSD/contrib/unbound/doc/
HDFEATURES27 RFC 1123, 6.1 Requirements for DNS of internet hosts.
41 RFC 4697: No DNS Resolution Misbehavior.
45 service. In fact for all DNS service so cache snooping is halted.
67 This is not a DNS statistics package, but some operationally useful
HDREADME.tests11 * dig - from the bind-tools package. Used to send DNS queries.
14 * ldns-testns - from ldns examples. Used as DNS auth server.
HDrequirements.txt14 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.
/NextBSD/usr.sbin/bsdconfig/networking/include/
HDmessages.subr46 msg_dns_configuration="DNS Nameserver Configuration:\nChoose Exit when finished else Cancel."
47 msg_dns_nameservers="DNS nameservers"
84 msg_please_enter_nameserver="Please enter the new IP address of the DNS nameserver:"
85 msg_please_enter_nameserver_existing="Please enter the new IP address of the DNS nameserver\n(set t…
89 msg_removing_nameserver="Removing DNS nameserver from resolv.conf(5)..."
96 msg_saving_nameserver="Saving new DNS nameserver to resolv.conf(5)..."
97 msg_saving_nameserver_existing="Editing DNS nameserver in resolv.conf(5)..."
104 xmsg_please_enter_nameserver_existing="Please enter the new IP address of the DNS nameserver\n(set …
/NextBSD/contrib/ntp/scripts/update-leap/
HDupdate-leap-opts.def28 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
/NextBSD/usr.sbin/bsdconfig/share/media/
HDhttp.subr267 # ^^^ IPv6 above / DNS Name or IPv4 below vvv
269 *:*/*) # DNS name or IPv4 address with port and directory
271 "DNS name or IPv4 addr" "$hostname"
277 *:*) # DNS name or IPv4 address with port
278 f_dprintf "Looks like a DNS name or IPv4 addr with port: %s" \
283 */*) # DNS name or IPv4 address with directory
284 f_dprintf "Looks like a DNS name or IPv4 addr with dir: %s" \
289 *) # DNS name or IPv4 address
290 f_dprintf "Looks like a DNS name or IPv4 addr: %s" "$hostname"
316 f_dprintf "Found DNS entry for %s successfully." "$hostname"
[all …]
HDftp.subr380 # ^^^ IPv6 above / DNS Name or IPv4 below vvv
382 *:*/*) # DNS name or IPv4 address with port and directory
384 "DNS name or IPv4 addr" "$hostname"
390 *:*) # DNS name or IPv4 address with port
391 f_dprintf "Looks like a DNS name or IPv4 addr with port: %s" \
396 */*) # DNS name or IPv4 address with directory
397 f_dprintf "Looks like a DNS name or IPv4 addr with dir: %s" \
402 *) # DNS name or IPv4 address
403 f_dprintf "Looks like a DNS name or IPv4 addr: %s" "$hostname"
429 f_dprintf "Found DNS entry for %s successfully." "$hostname"
[all …]
/NextBSD/crypto/openssl/doc/crypto/
HDX509_check_host.pod61 addresses stored in DNS names and Common Names are ignored.
85 one subject alternative name of the right type (DNS name or email
97 constitutes the complete label of a DNS name (e.g. "*.example.com")
105 would match a peer certificate with a DNS name of "www.example.com",
106 but would not match a peer certificate with a DNS name of
/NextBSD/crypto/heimdal/doc/
HDkerberos4.texi49 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
/NextBSD/contrib/ntp/sntp/
HDsntp-opts.def26 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
/NextBSD/etc/
HDhosts.allow29 # Protect against simple DNS spoofing attacks by checking that the
32 # 20 seconds is logged. No protection is afforded against DNS poisoning,
33 # IP spoofing or more complicated attacks. Hosts with no reverse DNS
/NextBSD/share/examples/IPv6/
HDUSAGE215 resolved by DNS. Specify the "-w" option to "ping6".
489 EDNS0 is defined in RFC2671. With EDNS0, the resolver library can tell DNS
490 server of its receiving buffer size, and permit DNS server to transmit large
497 KAME box -----------------------------> BIND9 DNS server
498 KAME box <----------------------------- BIND9 DNS server
499 can transmit jumbo reply, since DNS server
503 - prepare KAME box and BIND9 DNS server (can be a same node)
511 - BIND 4/8 DNS server will choke with EDNS0 packet, so you must not
512 turn the option on if you have BIND 4/8 DNS server. If you enable
513 "options edns0" against BIND 4/8 DNS server, you will never be able
[all …]
/NextBSD/contrib/netbsd-tests/ipf/input/
HDni14189 … 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.…
197 …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.…
HDni16189 … 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.…
197 …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.…
HDni15189 … 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.…
197 …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.…
HDni13185 … 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.…

1234567