As Fly is “decommissioning some legacy WireGuard gateways” I’m having to create new WireGuard VPN peers in LHR* 
.
Alas is seems that some of the new peers aren’t in Fly’s Private Network DNS (newpeername._peer.internal) 
. Other newly created WireGuard peers are appearing in Fly’s DNS.
Is this a known problem?
ugh, I thought I fixed this! can you give me the name of a peer that failed to add to DNS so I can take a look?
I’ve emailed the details to the support email address; any peers I created yesterday will have the -250731 suffix (e.g. others also may not be DNS).
thanks, we’re looking at it.
we are working to find the root cause of this issue. for now, I manually re-ran the job to add your organization’s peers to DNS; do you need anything else to be fixed or is that enough?
That should be enough for the moment, until I need to generate new peers (not planned in the immediate future).
Please confirm once the root cause has been identified and resolved (and ideally a proactive test on Fly’s part, e.g. scheduled Peer<>DNS diff, to catch if this occurs again in future). Thanks.
I’m running into this same problem, with at least one of my orgs.
@sax please email me at [email removed] and I can fix the DNS for your peers.
I’m confident we’ve resolved this issue for any new peers; we’ve also fixed the issue for any peer created in the last month. please let me know if anyone is still having trouble with it