> For the complete documentation index, see [llms.txt](https://docs.dnsvault.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dnsvault.net/service-management/dns/servers.md).

# Servers

You can navigate to servers:

{% hint style="info" %}
SIDE BAR > SERVICE MANAGEMENT > DNS > SERVERS
{% endhint %}

The **server** clause allows certain characteristics to be defined when this server is interacting with the remote server defined by (IPv4 or IPv6). The IP Address will only take a single IP value. There may be any number of **server** statements.

There is no requirement to have any server statements in which case default behaviours for all remote servers will be used.

### **BOGUS**

Indicates that traffic from this server should be ignored e.g. if known to be giving bad data, generating a DoS attack or some other reason. This statement can be used in the server clause only.

### EDNS

 Defines whether to use EDNS (RFC 2671) with a specific server (yes) or not (no). The default is yes. This statement may only be used in a server clause.

### KEYS

 The key-name field references a key clause with the same key-name and mandates that TSIG transactions (zone transfer or DDNS operation) with use this key. While syntax allows for multiple keys current versions of BIND (9.x) only support a single key-name per server. This statement may only be used in a server clause.

### TRANSFERS

Limits the number of concurrent zone transfers from any given server. If not present the default for transfers-per-ns is used. This option may be specified only in a server clause.<br>

![](https://2014779496-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MdQaZzI76y0iDZ955DD%2F-MecNDY4tDHZflQ1CpE2%2F-MecPRYoB-0znhBQdf2a%2Fimage.png?alt=media\&token=1fc7db3f-9fe7-4aab-abdf-68d408e48102)