Does auto wake (auto_start_machines) work with UDP?

Questions / Help
1

I’ve deployed my own authoritative name server to Fly and would ideally like it to scale-to-zero. Using this config:

[[services]]
internal_port = 53
protocol = "udp"
auto_stop_machines = true
auto_start_machines = true
min_machines_running = 0

[[services.ports]]
port = 53

I noticed that after all machines stop, sending a UDP packet to the server (via allocated IPv4 address, since UDP over IPv6 is not yet supported) does not trigger the machine to start. But if I serve a web server alongside the name server and expose it:

[[services]]
internal_port = 80
protocol = "tcp"
auto_stop_machines = true
auto_start_machines = true
min_machines_running = 0

[[services.ports]]
handlers = ["tls", "http"]
port = 443

Then sending an HTTP request successfully starts the machine. Also confirmed that the name server does successfully response to UDP packets after the machine has started.

Just hoping to confirm this behaviour for UDP and whether or not there are any plans to support it in the future.

2

AFAIK it’s a function of Fly’s proxies that wake up machines; I don’t believe the wake-up functionality works with UDP - so (currently) TCP only.

1 Like
3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.