did `top1.nearest.of` stop resolving?

my Sentry is flooded with the following error:

could not translate host name "top1.nearest.of.switchboard-dba.internal" to address: No address associated with hostname (PG::ConnectionBad)

started around midnight and took my app down.

worth noting, I haven’t changed anything. last deployment happened 2 days ago I think and it was working just fine since then

Hi… It worked for me when I just tried it, although these days Flycast is usually the better choice. Perhaps you have a really old Postgres instance? (The newer ones default to Flycast.)

One caveat is that there must be at least one Machine actually running in the switchboard-dba app, otherwise DNS will give an empty response to that query.

Hope this helps!

Perhaps you have a really old Postgres instance?

It is old but I have recreated this instance recently from scratch

One caveat is that there must be at least one Machine actually running in the switchboard-dba app, otherwise DNS will give an empty response to that query.

yes, there is one machine running, always have been

I ended up reattaching the database using fly postgres attach but now I have lost the top1 resolution which doesn’t make any sense

It worked for me when I just tried it,

definitely wasn’t working for me :grinning_face:

Hm… Possibly a localized side effect of the following?

Either way, it sounds like you have a working connection to the database now, which is the main thing.

If you have only a single Machine in switchboard-dba, then the top1 query wasn’t really doing anything for you anyway…

(Although it’s perfectly reasonable to wonder why it stopped working!)

1 Like

that would explain! and yeah, I had multiple machines but have scaled in since so right now top1 is not doing me anything, I will keep as/is

Thanks a lot!

1 Like