How AustNet is structured: servers and routing

AustNet is powered by InspIRCd, a modern, modular, and lightweight C++ Internet Relay Chat daemon. Like many large-scale networks, AustNet achieves global reach, high availability, and fault tolerance by linking multiple individual servers together into a single unified network.

1. How IRC Servers Link Together

An IRC network is rarely just a single computer. Instead, it is a mesh of multiple independent servers (nodes) that communicate using a server-to-server spanning tree protocol.

1. The Spanning Tree Model: Servers form direct cryptographic and authenticated links with neighboring servers. When a message or command is sent on one server, it is efficiently propagated across the links to all other connected servers.
2. Unified State: Thanks to this backend routing, a user connected to a server in Sydney shares the exact same channel list, user visibility, and communication pathways as someone connected via a node in another region. To the end user, the distributed cluster acts as a single entity.
3. Modular Architecture: Because AustNet uses InspIRCd, individual server operators can load specific security, routing, and tracking modules while maintaining protocol compatibility across the wider network.

2. What irc.austnet.org Resolves To

When you configure your IRC client, you rarely connect to a specific physical machine IP address. Instead, you use a network-wide DNS entry like irc.austnet.org.

1. Round-Robin DNS: irc.austnet.org utilizes DNS load balancing (often round-robin or geo-DNS) to point clients to a pool of available server IPs.
2. Automatic Distribution: Every time you restart your client or reconnect, the DNS lookup dynamically assigns you to one of the active backend nodes. This prevents any single server from becoming overloaded with thousands of simultaneous client connections.

3. What to Do If One Server Is Unreachable

Because networks rely on multiple linked nodes, occasional routing hiccups, maintenance windows, or unexpected node outages can cause a specific server to go offline. If your client drops or fails to connect, follow these troubleshooting steps:

1. Reconnect to the Pool First: If you were hardcoded to a specific regional server address that is down, restart your connection using the generic pool address (irc.austnet.org). This forces a fresh DNS query and routes you to a healthy, online node.
2. Try Alternative Ports: Ensure your client is trying standard secure ports (such as 6697 for SSL/TLS connections). Sometimes a local firewall or restrictive network blocks specific legacy ports.
3. Check Network Status Channels or Socials: If the entire network or major backbone links are experiencing an issue, check AustNet’s official support channels or web presence for announcements regarding scheduled maintenance or unexpected outages.
4. Configure Client Fallbacks: Modern IRC clients allow you to set up backup servers within the same network profile. If your primary connection drops, the client will automatically cycle through alternative servers until it establishes a stable link.