Getting timeout on digging pihole

Hello, tried this blog post to deploy a container. I’m able to access the webui, but unable to access the DNS at port 53.

This is my fly.toml

# fly.toml file generated for <redacted> on 2021-08-14T08:38:00+05:30

app = "<redacted>"

kill_signal = "SIGINT"
kill_timeout = 5


  allowed_public_ports = []
  auto_rollback = true

  http_checks = []
  internal_port = 80
  protocol = "tcp"
  script_checks = []

    hard_limit = 25
    soft_limit = 20
    type = "connections"

    handlers = ["http"]
    port = 80

    handlers = ["tls", "http"]
    port = 443

    grace_period = "1s"
    interval = "15s"
    restart_limit = 6
    timeout = "2s"

  internal_port = 53
  protocol = "udp"

    port = "53"

when doing a dig with the IPv4 (as well as IPv6), I’m getting the following:

dig @<anycast ip>
; <<>> DiG 9.16.1-Ubuntu <<>> @<anycast ip>
;; global options: +cmd
;; connection timed out; no servers could be reached

and telnet:

telnet <anycast ip> 53
Trying <anycast ip>...
Connected to <anycast ip>.
Escape character is '^]'.
Connection closed by foreign host.

fly logs:

2021-08-14T03:11:30.722691069Z runner[9ab56133] maa [info] Configuring virtual machine
2021-08-14T03:11:30.725124202Z runner[9ab56133] maa [info] Pulling container image
2021-08-14T03:11:33.799697025Z runner[9ab56133] maa [info] Unpacking image
2021-08-14T03:11:33.810900517Z runner[9ab56133] maa [info] Preparing kernel init
2021-08-14T03:11:34.064715306Z runner[9ab56133] maa [info] Configuring firecracker
2021-08-14T03:11:34.555668637Z runner[9ab56133] maa [info] Starting virtual machine
2021-08-14T03:11:34.690749408Z app[9ab56133] maa [info] Starting init (commit: edcd360)...
2021-08-14T03:11:34.707178915Z app[9ab56133] maa [info] Running: `/s6-init` as root
2021-08-14T03:11:34.719082762Z app[9ab56133] maa [info] 2021/08/14 03:11:34 listening on [fdaa:0:2fc5:a7b:1449:9ab5:6133:2]:22 (DNS: [fdaa::3]:53)
2021-08-14T03:11:34.762698950Z app[9ab56133] maa [info] [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
2021-08-14T03:11:34.790254473Z app[9ab56133] maa [info] [s6-init] ensuring user provided files have correct perms...exited 0.
2021-08-14T03:11:34.791916906Z app[9ab56133] maa [info] [fix-attrs.d] applying ownership & permissions fixes...
2021-08-14T03:11:34.794317583Z app[9ab56133] maa [info] [fix-attrs.d] 01-resolver-resolv: applying...
2021-08-14T03:11:34.798444042Z app[9ab56133] maa [info] [fix-attrs.d] 01-resolver-resolv: exited 0.
2021-08-14T03:11:34.799254674Z app[9ab56133] maa [info] [fix-attrs.d] done.
2021-08-14T03:11:34.800589184Z app[9ab56133] maa [info] [cont-init.d] executing container initialization scripts...
2021-08-14T03:11:34.802237368Z app[9ab56133] maa [info] [cont-init.d] executing...
2021-08-14T03:11:34.858324351Z app[9ab56133] maa [info]  ::: Starting docker specific checks & setup for docker pihole/pihole
2021-08-14T03:11:34.875074122Z app[9ab56133] maa [info]   [i] Installing configs from /etc/.pihole...
2021-08-14T03:11:34.877918599Z app[9ab56133] maa [info]   [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf
2021-08-14T03:11:35.029433642Z app[9ab56133] maa [info] Existing DNS servers detected in setupVars.conf. Leaving them alone
2021-08-14T03:11:35.051310516Z app[9ab56133] maa [info]   [✓] New password set
2021-08-14T03:11:35.051757331Z app[9ab56133] maa [info] DNSMasq binding to default interface: eth0
2021-08-14T03:11:35.069830997Z app[9ab56133] maa [info] Added ENV to php:
2021-08-14T03:11:35.070986294Z app[9ab56133] maa [info] 			"PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",
2021-08-14T03:11:35.071369040Z app[9ab56133] maa [info] 			"ServerIP" => "",
2021-08-14T03:11:35.071700786Z app[9ab56133] maa [info] 			"CORS_HOSTS" => "",
2021-08-14T03:11:35.072110942Z app[9ab56133] maa [info] 			"VIRTUAL_HOST" => "",
2021-08-14T03:11:35.076194246Z app[9ab56133] maa [info] Using IPv4 and IPv6
2021-08-14T03:11:35.077622350Z app[9ab56133] maa [info] ::: setup_blocklists now setting default blocklists up:
2021-08-14T03:11:35.078596199Z app[9ab56133] maa [info] ::: TIP: Use a docker volume for /etc/pihole/adlists.list if you want to customize for first boot
2021-08-14T03:11:35.079177842Z app[9ab56133] maa [info] ::: Blocklists (/etc/pihole/adlists.list) now set to:
2021-08-14T03:11:35.080188991Z app[9ab56133] maa [info]
2021-08-14T03:11:35.113012732Z app[9ab56133] maa [info] ::: Testing pihole-FTL DNS: FTL started!
2021-08-14T03:11:35.149075726Z app[9ab56133] maa [info] ::: Testing lighttpd config: Syntax OK
2021-08-14T03:11:35.150099875Z app[9ab56133] maa [info] ::: All config checks passed, cleared for startup ...
2021-08-14T03:11:35.152357319Z app[9ab56133] maa [info] ::: Enabling Query Logging
2021-08-14T03:11:35.156928588Z app[9ab56133] maa [info]   [i] Enabling logging...
  [✓] Logging has been enabled!
2021-08-14T03:11:35.159484179Z app[9ab56133] maa [info]  ::: Docker start setup complete
2021-08-14T03:11:35.160186122Z app[9ab56133] maa [info]   Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
2021-08-14T03:11:35.169631695Z app[9ab56133] maa [info]   Pi-hole version is v5.3.1 (Latest: v5.3.1)
2021-08-14T03:11:35.173286134Z app[9ab56133] maa [info]   AdminLTE version is v5.5.1 (Latest: v5.5.1)
2021-08-14T03:11:35.176375679Z app[9ab56133] maa [info]   FTL version is v5.8.1 (Latest: v5.8.1)
2021-08-14T03:11:35.177169790Z app[9ab56133] maa [info] [cont-init.d] exited 0.
2021-08-14T03:11:35.178053990Z app[9ab56133] maa [info] [cont-init.d] done.
2021-08-14T03:11:35.179256747Z app[9ab56133] maa [info] [services.d] starting services
2021-08-14T03:11:35.185823153Z app[9ab56133] maa [info] Starting lighttpd
2021-08-14T03:11:35.190267053Z app[9ab56133] maa [info] Starting pihole-FTL (no-daemon) as root
2021-08-14T03:11:35.192929653Z app[9ab56133] maa [info] Starting crond
2021-08-14T03:11:35.219010980Z app[9ab56133] maa [info] Stopping pihole-FTL
2021-08-14T03:11:35.234955451Z app[9ab56133] maa [info] [services.d] done.
2021-08-14T03:11:35.712358812Z app[9ab56133] maa [info] Reaped child process with pid: 586, exit code: 0
2021-08-14T03:11:35.713465979Z app[9ab56133] maa [info] Reaped child process with pid: 601, exit code: 0
2021-08-14T03:11:35.714542277Z app[9ab56133] maa [info] Reaped child process with pid: 616, exit code: 0
2021-08-14T03:11:35.715623325Z app[9ab56133] maa [info] Reaped child process with pid: 624, exit code: 0
2021-08-14T03:11:35.716638243Z app[9ab56133] maa [info] Reaped child process with pid: 653, exit code: 0
2021-08-14T03:11:35.717309526Z app[9ab56133] maa [info] Reaped child process with pid: 682, exit code: 0
2021-08-14T03:11:35.717958149Z app[9ab56133] maa [info] Reaped child process with pid: 690, exit code: 0
2021-08-14T03:11:35.718619051Z app[9ab56133] maa [info] Reaped child process with pid: 698, exit code: 0
2021-08-14T03:11:35.719374243Z app[9ab56133] maa [info] Reaped child process with pid: 717, exit code: 0
2021-08-14T03:11:35.720315882Z app[9ab56133] maa [info] Reaped child process with pid: 706, exit code: 0
2021-08-14T03:11:35.721246782Z app[9ab56133] maa [info] Reaped child process with pid: 707, exit code: 0
2021-08-14T03:11:35.722207381Z app[9ab56133] maa [info] Reaped child process with pid: 846, exit code: 0
2021-08-14T03:11:35.723637655Z app[9ab56133] maa [info] Reaped child process with pid: 848 and signal: SIGKILL, core dumped? false
2021-08-14T03:11:35.724583534Z app[9ab56133] maa [info] Reaped child process with pid: 733, exit code: 0
2021-08-14T03:11:35.725558263Z app[9ab56133] maa [info] Reaped child process with pid: 734, exit code: 0
2021-08-14T03:11:36.189014200Z app[9ab56133] maa [info] Starting pihole-FTL (no-daemon) as root
2021-08-14T03:11:46.246470654Z proxy[9ab56133] maa [info] Health check status changed 'warning' => 'passing'

not sure what i’m doing wrong?

i tried with adguard too and it looks like i’m able to connect via TCP, but UDP somehow times out. may be a problem on side?

any updates on this please?

Sorry for the huge delay in responding to this. It seems to have slipped through the cracks.

Can you try re-deploying if you haven’t in the past week or so? We have some servers where UDP doesn’t work the way it should. Apps with UDP are now constrained to servers that do support it now. Your region might be unavailable though.

Thanks for looking into this. Anywhere I can track this issue? and what regions UDP is available now?

The following regions should work for UDP: ams, atl, cdg, dfw, ewr, fra, hkg, iad, lax, lhr, nrt, ord, scl, sea, sin, sjc, syd, vin, yyz

thanks! please let me know if it’s available on maa.

Hello, is the UDP support added for MAA region?

I am also looling forward to UDP in ‘maa’ region. Any updates on this?
In addition to that I am also looking forward to regional ip-v4 in ‘maa’ region. I was able to allocate a regional ip-v4 for sydney but doing so for maa region led to an error