Searched refs:DNS (Results 1 – 21 of 21) sorted by relevance
| /linux-4.4.14/net/dns_resolver/ |
| D | Kconfig | 2 # Configuration for DNS Resolver
5 tristate "DNS Resolver support"
8 Saying Y here will include support for the DNS Resolver key type
9 which can be used to make upcalls to perform DNS lookups in
12 DNS Resolver is used to query DNS server for information. Examples
14 performing a DNS query for AFSDB records so that AFS can locate a
17 DNS Resolver is used by the CIFS and AFS modules, and would support
18 SMB2 later. DNS Resolver is supported by the userspace upcall
|
| /linux-4.4.14/Documentation/networking/ |
| D | dns_resolver.txt | 2 DNS Resolver Module
19 The DNS resolver module provides a way for kernel services to make DNS queries
42 CONFIG_DNS_RESOLVER - tristate "DNS Resolver support"
76 This is the basic access function. It looks for a cached DNS query and if
77 it doesn't find it, it upcalls to userspace to make a new DNS query, which
100 DNS lookup failed.
111 READING DNS KEYS FROM USERSPACE
123 this type are used to transport and cache DNS lookup results from userspace.
126 keyrings for a cached DNS result. If that fails to find one, it upcalls to
133 The upcall handler program is responsible for querying the DNS, processing the
|
| D | 00-INDEX | 72 - The DNS resolver module allows kernel servies to make DNS queries.
|
| D | README.sb1000 | 119 see if the networking is running but the DNS resolution is where the
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | nfs.txt | 57 The DNS resolver
68 a path, or a DNS hostname and a path. The latter requires the NFS client to
69 do a DNS lookup in order to mount the new volume, and hence the need for an
99 as having no valid DNS translation.
|
| D | 00-INDEX | 10 - nfs client, and DNS resolution for fs_locations.
|
| D | nfsroot.txt | 129 be carried in the DHCP request to hopefully update DNS record.
|
| /linux-4.4.14/fs/nfs/ |
| D | Kconfig | 143 the format of a DNS domain name and should be set to the DNS domain
183 bool "Use the legacy NFS DNS resolver"
187 IP address. Select Y here if you would rather use your own DNS
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | kirkwood-dns320.dts | 6 model = "D-Link DNS-320 NAS (Rev A1)";
|
| D | kirkwood-dns325.dts | 6 model = "D-Link DNS-325 NAS (Rev A1)";
|
| D | armada-370-dlink-dns327l.dts | 2 * Device Tree file for D-Link DNS-327L
56 model = "D-Link DNS-327L";
|
| D | kirkwood-dnskw.dtsi | 5 model = "D-Link DNS NASes (kirkwood-based)";
|
| /linux-4.4.14/net/ceph/ |
| D | Kconfig | 32 bool "Use in-kernel support for DNS lookup"
|
| /linux-4.4.14/tools/hv/ |
| D | hv_kvp_daemon.c | 78 DNS enumerator
1170 case DNS: in process_ip_string()
1175 if (type == DNS) { in process_ip_string()
1196 case DNS: in process_ip_string()
1201 if (type == DNS) { in process_ip_string()
1340 error = process_ip_string(file, (char *)new_val->dns_addr, DNS); in kvp_set_ip_info()
|
| /linux-4.4.14/arch/arm/mach-orion5x/ |
| D | Kconfig | 47 bool "D-Link DNS-323"
52 D-Link DNS-323 platform.
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | afs.txt | 224 to my internal DNS. My "root.afs" partition has a mount point within it for
|
| D | coda.txt | 462 form of a Ipv6 size IP address naming the Coda cell through DNS.
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | kernel.txt | 290 hostname "darkstar" and DNS (Internet Domain Name Server)
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | CHANGES | 184 handle DNS host to ipv6 name translation). Accept override of uid or gid
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 1729 UML, such as 10.0.2.3 which is an alias for the DNS server specified
4574 Chris Reahard built a specialized root filesystem for running a DNS
|
| /linux-4.4.14/Documentation/security/ |
| D | keys.txt | 573 DNS resolver cache keyring is an example of this.
|