The implementations of DNS and the Crossfire metaserver expect a range of known IP addresses for an address to be in. The Crossfire metaserver appears to expect a resolvable domain name or a static IP.

It appears, though, that by determining the Crossfire server's public IP address before each time it reports to the metaserver, we should be able to have a server hosted on a dynamic IP range controlled by an ISP, without having to set up a static IP nor a DNS entry. This would have the net effect of a few stale entries occasionally lingering in the metaserver itself, but those will be removed like any other server that stops sending updates to it, bring removed after a set amount of time.
This project is an attempt to implement that as a workaround, because I don't feel like interacting with my ISP nor DNS providers.

Project Activity

See All Activity >

License

GNU General Public License version 2.0 (GPLv2)

Follow cf-dynamic-address

cf-dynamic-address Web Site

Other Useful Business Software
Custom VMs From 1 to 96 vCPUs With 99.95% Uptime Icon
Custom VMs From 1 to 96 vCPUs With 99.95% Uptime

General-purpose, compute-optimized, or GPU/TPU-accelerated. Built to your exact specs.

Live migration and automatic failover keep workloads online through maintenance. One free e2-micro VM every month.
Try Free
Rate This Project
Login To Rate This Project

User Reviews

Be the first to post a review of cf-dynamic-address!

Additional Project Details

User Interface

Non-interactive (Daemon)

Programming Language

C

Related Categories

C Role-Playing Games (RPG), C Multi-User Dungeons (MUD) Game, C Multiplayer Game

Registered

2021-01-13