|
Size: 1799
Comment:
|
Size: 628
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 12: | Line 12: |
| passwd: compat group: compat shadow: compat hosts: dns [!UNAVAIL=return] files networks: nis [NOTFOUND=return] files ethers: nis [NOTFOUND=return] files protocols: nis [NOTFOUND=return] files rpc: nis [NOTFOUND=return] files services: nis [NOTFOUND=return] files |
nameserver 8.8.8.8 search lan |
| Line 29: | Line 22: |
| === Databases === | The resolver configuration file primariliy consists of two directives: `nameserver` and `search` (as in 'search domain'). |
| Line 31: | Line 24: |
| The first column (delimited by spaces or tab characters) indicates a database, while every subsequent column is a source. Some common database sources are listed below. | There should be up to '''three''' `nameserver` directives, giving some address that can be reached for queries. |
| Line 33: | Line 26: |
| For `hosts`... * `files` (i.e. `/etc/hosts`) * `dns` (i.e. run-time lookups based on `/etc/resolv.conf`) * `myhostname` (see `nss-myhostname(8)`) * `mymachine` which connects to `systemd-machined` (see `nss-mymachines(8)`) * `resolve` which connects to `systemd-resolved` (see `nss-resolve(8)`) ---- === Action Items === '''Action items''' follow one the following patterns: `[STATUS=ACTION]` and `[!STATUS=ACTION]`. `STATUS` can be any of... * `success` meaning 'no error'. * `notfound` meaning 'error in lookup'. * `unavail` indicates a connection couldn't be made. * `tryagain` indicates 'temporarily unavailability', as with locked connections. `ACTION` can be any of... * `return` meaning 'return the result' * `continue` meaning 'try the next item' * `merge` causes the system to try both the preceding and the following items, and By default, only a `success` status results in a `return` action. Anything else will result in a `continue`. The exception is for a `group` lookup-a `notfound` status will lead to a `continue` action regardless of any action specified. |
Search domains are used in an attempt to qualify non-fully-qualified names. For instance, given `search localdomain` in `/etc/resolv.conf`, a system will attempt to resolve `myhost` as `myhost.localdomain` first. |
resolv.conf
Contents
Example
nameserver 8.8.8.8 search lan
Syntax
The resolver configuration file primariliy consists of two directives: nameserver and search (as in 'search domain').
There should be up to three nameserver directives, giving some address that can be reached for queries.
Search domains are used in an attempt to qualify non-fully-qualified names. For instance, given search localdomain in /etc/resolv.conf, a system will attempt to resolve myhost as myhost.localdomain first.