DWShells:IPv6 and DNS

IPv6, DNS and assigned application ports

Understand which address and port belongs to SSH, your website and your IRC applications.

Last verified: 6 October 2026. This page covers the connection policy and basic panel workflow. Follow the current fields and validation shown in the panel for hostname changes.

← Documentation hub

Three different connections

Connection	Where to get its settings
SSH / SFTP	Shell Access and shell connection details; shared login host shells.darkworld.network
Personal website	The selected shell's personal HTTPS link
ZNC / Eggdrop listener	Packages, for the selected app instance; use its assigned listener port and TLS details

A hostname can point to the same server while a port selects a different service. Do not enter an application's port in your SSH settings or use the network's IRC server port as your ZNC listener port.

Inbound versus outbound

Direction	Meaning	Policy
Client → application	Your IRC client connects to your shell's ZNC listener	Use assigned addresses/port. IPv4 requires confirmed forwarding.
Application → IRC network	ZNC, Eggdrop or an IRC client connects outward	Free uses IPv6 for IRC. Other permitted plans prefer assigned IPv6 with allowed IPv4 fallback.

Inbound IPv4 forwarding does not grant a Free shell outbound IPv4 IRC access. Use only your assigned bind addresses and ports. Do not create tunnels or proxies to evade restrictions.

Inspect IPv6 and DNS

1. Select the correct shell in the customer panel.
2. Open IPv6 / DNS and read the current addresses, hostname information and status.
3. Use Refresh DNS status to read current records and pending operations.
4. If the portal offers an extra managed hostname, select an assigned IPv6 address and supply the allowed hostname label.
5. Review the result and any queued or running operation; wait for its completion before expecting the hostname to work.

Do not copy an address from another user's guide or account. Field availability and hostname validation depend on the current panel and your allocation.

DNS records and certificates

An A record maps a hostname to an IPv4 address; an AAAA record maps it to an IPv6 address. Reverse DNS is a separate mapping from an address back to a name. None of these records alone grants an application port, confirms forwarding or issues a valid TLS certificate for an arbitrary hostname.

Use the hostname and certificate information displayed by the application manager. If the name does not match the certificate, ask staff to review it rather than disabling verification. A DNS change may not immediately replace records cached by your device or resolver.

Troubleshooting

Symptom	Check
Website works, ZNC fails	The ZNC process, allocated listener port, TLS and forwarding status; these are separate from HTTPS hosting.
ZNC works via IPv6, IPv4 fails	Confirm the manager explicitly reports IPv4 forwarding for that listener. Report the port and error to staff without credentials.
ZNC accepts a client but its network is offline	Check outbound network/server/port/TLS and IPv6 support on Free.
New hostname is unavailable	Check job status and DNS records; verify it points to your assignment and account for cached records.
IRC network is blocked	Request staff review of the network; do not bypass approved-destination rules.

References

• Signup and Rules
• ZNC guide
• Eggdrop guide
• Customer panel