Home
last modified time | relevance | path

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

1234567891011

/third_party/grpc/templates/test/cpp/naming/
Dresolver_component_tests_defs.include32 help='Path to local DNS server python script.')
34 help=('Path to DNS records yaml file that '
35 'specifies records for the DNS sever. '))
37 help=('Port that local DNS server is listening on.'))
39 help=('Path to the DNS health check utility.'))
67 test_runner_log('Health check: attempt to connect to DNS server over TCP.')
76 'query to DNS server.'))
86 test_runner_log(('DNS server is up! '
92 test_runner_log(('Failed to reach DNS server over TCP and/or UDP. '
94 test_runner_log('======= DNS server stdout '
[all …]
/third_party/curl/docs/cmdline-opts/
Ddns-interface.d3 Help: Interface to use for DNS requests
4 Protocols: DNS
10 Tell curl to send outgoing DNS requests through <interface>. This option is a
11 counterpart to --interface (which does not affect DNS). The supplied string variable
Ddns-ipv4-addr.d3 Help: IPv4 address to use for DNS requests
4 Protocols: DNS
10 Tell curl to bind to <ip-address> when making IPv4 DNS requests, so that
11 the DNS requests originate from this address. The argument should be a
Ddns-ipv6-addr.d3 Help: IPv6 address to use for DNS requests
4 Protocols: DNS
10 Tell curl to bind to <ip-address> when making IPv6 DNS requests, so that
11 the DNS requests originate from this address. The argument should be a
Ddns-servers.d3 Help: DNS server addrs to use
8 Set the list of DNS servers to be used instead of the system default.
/third_party/node/doc/api/
Ddns.md1 # DNS chapter
12 Although named for the [Domain Name System (DNS)][], it does not always use the
13 DNS protocol for lookups. [`dns.lookup()`][] uses the operating system
27 All other functions in the `dns` module connect to an actual DNS server to
28 perform name resolution. They will always use the network to perform DNS
31 DNS queries, bypassing other name-resolution facilities.
59 An independent resolver for DNS requests.
122 Cancel all outstanding DNS queries made by this resolver. The corresponding
142 The resolver will use the v4 local address when making requests to IPv4 DNS
143 servers, and the v6 local address when making requests to IPv6 DNS servers.
[all …]
/third_party/node/test/fixtures/keys/
Ddns-cert1.cnf23 DNS.1 = google.com�.evil.com
24 DNS.2 = just-another.com
27 DNS.3 = last.com
/third_party/curl/tests/certs/
DServer-localhost-firstSAN-sv.prm3 subjectAltName = DNS:localhost,DNS:localhost1,DNS:localhost2
DServer-localhost-lastSAN-sv.prm3 subjectAltName = DNS:localhost1,DNS:localhost2,DNS:localhost
DServer-localhost-firstSAN-sv.pem3 subjectAltName = DNS:localhost,DNS:localhost1,DNS:localhost2
94 DNS:localhost, DNS:localhost1, DNS:localhost2
DServer-localhost-lastSAN-sv.pem3 subjectAltName = DNS:localhost1,DNS:localhost2,DNS:localhost
95 DNS:localhost1, DNS:localhost2, DNS:localhost
DServer-localhost-lastSAN-sv.crt43 DNS:localhost1, DNS:localhost2, DNS:localhost
/third_party/grpc/src/core/tsi/test_creds/
Dserver1-openssl.cnf23 DNS.1 = *.test.google.fr
24 DNS.2 = waterzooi.test.google.be
25 DNS.3 = *.test.youtube.com
Dmulti-domain-openssl.cnf24 DNS.1 = foo.test.domain.com
25 DNS.2 = bar.test.domain.com
/third_party/curl/tests/data/
Dtest151514 # the DNS cache timeout elapses and must succeed exactly like the first one.
49 caching of manual libcurl DNS entries after DNS cache timeout
Dtest151615 # not clean the DNS entries added manually.
45 caching of manual libcurl DNS entries after dead connection
/third_party/uboot/u-boot-2020.01/doc/
DREADME.dns4 The Domain Name System (DNS) is a hierarchical naming system for computers,
14 For more information on DNS - http://en.wikipedia.org/wiki/Domain_Name_System
16 U-Boot and DNS
58 For some helpful things that can be related to DNS in U-Boot,
/third_party/grpc/doc/
Dnaming.md5 gRPC supports DNS as the default name-system. A number of alternative
27 - `dns:[//authority/]host[:port]` -- DNS (default)
28 - `host` is the host to resolve via DNS.
32 - `authority` indicates the DNS server to use, although this is only
33 supported by some implementations. (In C-core, the default DNS
Denvironment_variables.md49 - cares_resolver - traces operations of the c-ares based DNS resolver
50 - cares_address_sorting - traces operations of the c-ares based DNS
142 Declares which DNS resolver to use. The default is ares if gRPC is built with
144 Available DNS resolver include:
145 - ares (default on most platforms except iOS, Android or Node)- a DNS
147 - native - a DNS resolver based around getaddrinfo(), creates a new thread to
/third_party/libwebsockets/READMEs/
DREADME.async-dns.md1 # Asynchronous DNS
5 Lws now features optional asynchronous, ie, nonblocking recursive DNS
17 Lws' asynchronous DNS resolver creates a caching name resolver
44 If enabled at cmake, the async DNS implementation is used automatically
57 DNS is a very old standard that has some quirks... one of them is that
81 Where CNAMEs are returned, DNS servers may take two approaches... if the
/third_party/node/deps/npm/node_modules/uuid/bin/
Duuid38 if (namespace == 'DNS') namespace = uuidV3.DNS;
57 if (namespace == 'DNS') namespace = uuidV5.DNS;
/third_party/python/Lib/test/
Didnsans.pem85DNS:idnsans, DNS:xn--knig-5qa.idn.pythontest.net, DNS:xn--knigsgsschen-lcb0w.idna2003.pythontest.n…
/third_party/curl/docs/
DROADMAP.md13 ## HTTPS DNS records
15 As a DNS version of alt-svc and also a pre-requisite for ECH (see below).
DCURL-DISABLE.md25 Disable DNS-over-HTTPS
111 Disable the shuffle DNS feature
/third_party/openssl/doc/man3/
DX509_check_host.pod61 addresses stored in DNS names and Common Names are ignored.
87 one subject alternative name of the right type (DNS name or email
93 names of the right type (DNS name or email address as appropriate); the default
108 constitutes the complete label of a DNS name (e.g. "*.example.com")
116 would match a peer certificate with a DNS name of "www.example.com",
117 but would not match a peer certificate with a DNS name of

1234567891011