vHost and BindHost Policy

[Eggy]

vHost and BindHost Policy

vHosts must be selected and applied through the approved dashboard vHost library.

Approved vHosts only

Users may only use vHosts made available to their account through the dashboard.

Availability may depend on:

• Account type.
• Premium entitlement.
• Address-family compatibility.
• The selected IRC network.
• Current service availability.

A vHost shown as Premium must not be used without an active Premium entitlement.

Do not bypass vHost controls

Users must not manually set BindHost to:

• Use a Premium-only vHost without Premium.
• Use an unapproved hostname.
• Use an IP address assigned to another account or option.
• Bypass dashboard restrictions.
• Avoid a previous vHost restriction.

Manual BindHost abuse may be identified through account, configuration and audit records.

Action for vHost abuse

Where abuse is confirmed, the account may remain usable, but the following restrictions may be applied:

• The unauthorised vHost may be removed.
• A generic provider-managed vHost may be assigned.
• The affected network may be reconnected.
• Manual BindHost changes may be disabled.
• Dashboard vHost changes may be restricted.
• Premium-only selections may be blocked.

These restrictions may remain in place to prevent repeated abuse.

IPv4 and IPv6 compatibility

Many approved vHosts use IPv6.

An IPv6 vHost cannot function through an IRC server that only supports IPv4.

Users may need to:

• Select an IPv6-capable IRC server.
• Choose an IPv4-compatible vHost.
• Use an available fallback option.

Changes to the vHost library

vHosts may be added, renamed, replaced or retired.

Where practical, users assigned to a retired vHost may be migrated to an appropriate replacement.

A brief network reconnect may be required before a changed vHost appears in WHOIS.