---
layout: docs
page_title: 'Commands: node config'
sidebar_title: config
description: |
  The node config command is used to view or modify client configuration.
---

# Command: node config

The `node config` command is used to view or modify client configuration
details. This command only works on client nodes, and can be used to update
the running client configurations it supports.

## Usage

```plaintext
nomad node config [options]
```

The arguments behave differently depending on the flags given. See each flag's
description below for specific usage information and requirements.

## General Options

@include 'general_options_no_namespace.mdx'

## Node Config Options

- `-servers`: List the client's known servers. Client nodes do not participate
  in the gossip pool, and instead register with these servers periodically over
  the network. The initial value of this list may come from configuration files
  using the [`servers`] configuration option in the client block.

  If ACLs are enabled, this option requires a token with the 'agent:read'
  capability.

- `-update-servers`: Updates the client's server list using the provided
  arguments. Multiple server addresses may be passed using multiple arguments.
  When updating the servers list, you must specify ALL of the server nodes you
  wish to configure. The set is updated atomically. It is an error to specify
  this flag without any server addresses. If you do _not_ specify a port for each
  server address, the default port `4647` will be used.

  If ACLs are enabled, this option requires a token with the 'agent:write'
  capability.

## Examples

Query the currently known servers:

```shell-session
$ nomad node config -servers
server1:4647
server2:4647
```

Update the list of servers:

```shell-session
$ nomad node config -update-servers server1:4647 server2:4647 server3:4647 server4

```

[`servers`]: /docs/configuration/client#servers
