> For the complete documentation index, see [llms.txt](https://diameter.learn-telecom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://diameter.learn-telecom.com/diameter-nodes/diameter-peers.md).

# Diameter Peers

Nodes with a direct TCP or SCTP transport connection are Peers. 

• A node SHOULD have a connection with at least two peers per realm (primary and secondary). 

• Peers may be statically configured or dynamically discovered 

• Static configuration requires: - either the IP address, or - the FQDN (DNS can then resolve FQDN into IP-address) 

• Dynamic discovery based on: - DNS procedures using NAPTR and/or SRV queries 

A new Peer creates an entry in the 

\- Peer Table, and 

\- Routing Table (for other realms) 

Entries created via DNS MUST be refreshed periodically. 

When no transport connection exists with a peer, an attempt to connect SHOULD be made periodically (recommended every 30 s).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://diameter.learn-telecom.com/diameter-nodes/diameter-peers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.