Consistent 75 second delay in provisioning proxy A record

[drewr]

With the recent develop branch (below was at 32f9627), proxy DNS has often (not every time, but frequently) taken 75 sec to propagate the A record to ns1-4.

% datumctl connect tunnel listen --endpoint localhost:8888
  ○ Your endpoint ID: 980e5d204ea88fa6a2271cc49854d303b9751894ff9e17dee330dc2369db7cf9
  ○ Setting up tunnel...
  ✓ connector ready (0.0s) [Connector/datum-connect-stncn]
  ✓ TLS certificate issued (0.0s) [HTTPProxy/tunnel-hxbjw]
  ✓ iroh DNS published (0.0s) [Connector/datum-connect-stncn]
  ✓ tunnel accepted (7.5s) [HTTPProxy/tunnel-hxbjw]
  ✓ route programmed (7.5s) [HTTPProxy/tunnel-hxbjw]
  ✓ checking for NS (0.1s) [datumproxy.net]: 67.14.161.128, 67.14.162.128, 67.14.163.128, 67.14.160.128
  ○ waiting for A record (5s) [oven-pit-nb5p4.datumproxy.net]
  ○ waiting for A record (10s) [oven-pit-nb5p4.datumproxy.net]
  ○ waiting for A record (15s) [oven-pit-nb5p4.datumproxy.net]
  ○ waiting for A record (20s) [oven-pit-nb5p4.datumproxy.net]
  ○ waiting for A record (25s) [oven-pit-nb5p4.datumproxy.net]
  ○ waiting for A record (30s) [oven-pit-nb5p4.datumproxy.net]
  ○ waiting for A record (35s) [oven-pit-nb5p4.datumproxy.net]
  ○ waiting for A record (40s) [oven-pit-nb5p4.datumproxy.net]
  ○ waiting for A record (45s) [oven-pit-nb5p4.datumproxy.net]
  ○ waiting for A record (50s) [oven-pit-nb5p4.datumproxy.net]
  ○ waiting for A record (56s) [oven-pit-nb5p4.datumproxy.net]
  ○ waiting for A record (61s) [oven-pit-nb5p4.datumproxy.net]
  ○ waiting for A record (66s) [oven-pit-nb5p4.datumproxy.net]
  ○ waiting for A record (71s) [oven-pit-nb5p4.datumproxy.net]
  ✓ DNS provisioned (75.6s) [oven-pit-nb5p4.datumproxy.net]: 67.14.168.1, 67.14.164.1
  ✓ origin reachable (0.0s) [http://localhost:8888]: HTTP 200
  ✓ proxy responding (0.2s) [https://oven-pit-nb5p4.datumproxy.net]: HTTP 200
Tunnel ready: https://oven-pit-nb5p4.datumproxy.net
Press Ctrl+C to stop...

[drewr]

And then from a separate machine minutes later, different behavior:

% datumctl connect tunnel listen --endpoint localhost:11434
  ○ Your endpoint ID: 8229925d0013b201d6e2b10cbd615a05fbeb986409545e304d3e0311e6877f97
  ○ Setting up tunnel...
  ✓ tunnel accepted (0.0s) [HTTPProxy/tunnel-bt28p]
  ✓ TLS certificate issued (0.0s) [HTTPProxy/tunnel-bt28p]
  ✓ iroh DNS published (0.0s) [Connector/datum-connect-mlvcc]
  ✓ route programmed (0.0s) [HTTPProxy/tunnel-bt28p]
  ✓ connector ready (0.3s) [Connector/datum-connect-mlvcc]
  ✓ checking for NS (0.0s) [datumproxy.net]: 67.14.163.128, 67.14.160.128, 67.14.162.128, 67.14.161.128
  ✓ DNS provisioned (0.0s) [flat-stove-my7y8.datumproxy.net]: 67.14.168.1, 67.14.164.1
  ✓ origin reachable (0.0s) [http://localhost:11434]: HTTP 200
  ○ waiting for tunnel [https://flat-stove-my7y8.datumproxy.net] (0s) ... HTTP 503
  ○ waiting for tunnel [https://flat-stove-my7y8.datumproxy.net] (10s) ... HTTP 503
  ○ waiting for tunnel [https://flat-stove-my7y8.datumproxy.net] (20s) ... HTTP 503
  ○ waiting for tunnel [https://flat-stove-my7y8.datumproxy.net] (30s) ... HTTP 503

[drewr]

Correction, after clearing out the existing connectors, I got the same behavior as the original machine:

% datumctl connect tunnel listen --endpoint localhost:11434
  ○ Your endpoint ID: 7d0bda4668bfd13ca119246843a00208f5cd112bcc20c8a152ed2172d89dcbc7
  ○ Setting up tunnel...
  ✓ connector ready (0.0s) [Connector/datum-connect-twcrs]
  ✓ TLS certificate issued (0.0s) [HTTPProxy/tunnel-858j6]
  ✓ iroh DNS published (0.0s) [Connector/datum-connect-twcrs]
  ✓ tunnel accepted (7.1s) [HTTPProxy/tunnel-858j6]
  ✓ route programmed (7.1s) [HTTPProxy/tunnel-858j6]
  ✓ checking for NS (0.1s) [datumproxy.net]: 67.14.162.128, 67.14.161.128, 67.14.163.128, 67.14.160.128
  ○ waiting for A record (5s) [mobile-unable-xdh79.datumproxy.net]
  ○ waiting for A record (10s) [mobile-unable-xdh79.datumproxy.net]
  ○ waiting for A record (15s) [mobile-unable-xdh79.datumproxy.net]
  ○ waiting for A record (20s) [mobile-unable-xdh79.datumproxy.net]
  ○ waiting for A record (25s) [mobile-unable-xdh79.datumproxy.net]
  ○ waiting for A record (30s) [mobile-unable-xdh79.datumproxy.net]
  ○ waiting for A record (35s) [mobile-unable-xdh79.datumproxy.net]
  ○ waiting for A record (40s) [mobile-unable-xdh79.datumproxy.net]
  ○ waiting for A record (45s) [mobile-unable-xdh79.datumproxy.net]
  ○ waiting for A record (50s) [mobile-unable-xdh79.datumproxy.net]
  ○ waiting for A record (55s) [mobile-unable-xdh79.datumproxy.net]
  ○ waiting for A record (60s) [mobile-unable-xdh79.datumproxy.net]
  ○ waiting for A record (65s) [mobile-unable-xdh79.datumproxy.net]
  ○ waiting for A record (70s) [mobile-unable-xdh79.datumproxy.net]
  ✓ DNS provisioned (75.2s) [mobile-unable-xdh79.datumproxy.net]: 67.14.168.1, 67.14.164.1
  ✓ origin reachable (0.0s) [http://localhost:11434]: HTTP 200
  ✓ proxy responding (0.1s) [https://mobile-unable-xdh79.datumproxy.net]: HTTP 200
Tunnel ready: https://mobile-unable-xdh79.datumproxy.net
Press Ctrl+C to stop...