fly dns now returning stale results for wg peers 1

1

since you auto-closed my other topic with no reply:

I’m still seeing bad data come back:


╰🡒  ip a |grep fdaa
    inet6 fdaa:0:4da4:a7b:28:0:a:102/120 scope global


╰🡒  flyctl wireguard list 'redact' | grep colemickens
| tube-colemickens           | bos    | fdaa:0:4da4:a7b:28:0:a:102    |



╰🡒   dig +noall +answer tube-colemickens._peer.internal aaaa @fdaa:0:4da4::3
tube-colemickens._peer.internal. 5 IN   AAAA    fdaa:0:4da4:a7b:ce2:0:a:102

I don’t get it. What do I need to do to get fly to return the correct results here?

This is … really frustrating and painful.

2

Yeah, I just don’t get it. I can restart this over and over and fly gaslights me:


╰🡒  dig +noall +answer tube-colemickens._peer.internal aaaa @fdaa:0:4da4::3
tube-colemickens._peer.internal. 5 IN   AAAA    fdaa:0:4da4:a7b:ce2:0:a:102


╰🡒  flyctl wireguard list 'redact | grep colemickens
| tube-colemickens          | fdaa:0:4da4:a7b:28:0:a:102    |
3

Hey @colemickens-ds

Sorry for the trouble. We had some stale data in the service discovery system that powers the DNS. Should be fixed now.

1 Like
4

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