Issues adding 2nd Peer to Wireguard w/PiVPN/Pihole/Unbound

[Icona]

I've had a raspberry pi with pihole/WireGuard/unbound working for quite some time now with zero issues. I tried adding another "Peer" to WireGuard and it connects, but no internet/DNS resolution and I can't access my network devices remotely. Adding the peer went pretty smoothly, but for some reason I cannot connect to the Internet. I'm pretty sure I'm overlooking a small port config or some other minor config, but I can't seem to figure this out. The iPhone peer has been setup and working properly for many months, just having issues getting the MacBook Pro to connect.

Here's what my wg0 config file looks like (Keys were removed obviously):

[Interface]
PrivateKey = private key
Address = 10.69.85.1/24
PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -A FORWARD -o wg0 -j AC>
PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -D FORWARD -o wg0 -j >
MTU = 1420
ListenPort = 51820

begin iPhone

[Peer]
PublicKey = public key
PresharedKey = preshared key
AllowedIPs = 10.69.85.3/32

end iPhone

begin MacBookPro

[Peer]
PublicKey = public key
PresharedKey = pre-shared key
AllowedIPs = 10.69.85.4/32

end MacBookPro

Here's what the Peer config files look like:
iPhone:

[Interface]
PrivateKey = private key
Address = 10.69.85.3/24
DNS = 10.69.85.1

[Peer]
PublicKey = public key
PresharedKey = pre-shared key
Endpoint = majestys-pihole.duckdns.org: port number
AllowedIPs = 0.0.0.0/0, ::0/0

MacBook Pro:

[Interface]
PrivateKey = private key
Address = 10.69.85.4/24
DNS = 10.69.85.1

[Peer]
PublicKey = public key
PresharedKey = pre-shared key
Endpoint = majestys-pihole.duckdns.org:port number
AllowedIPs = 0.0.0.0/0, ::0/0

As I previously stated I removed all the key's info due to privacy concerns and the the "Endpoint" port numbers are the same for both peers, which kind of bothers me. Maybe the issue could be the endpoint ports. I tried changing the ports on one of the peers but it did not work. Any ideas?

[Bucking_Horn]

This is a PiVPN/Wireguard issue, not a Pi-hole one.

Note that with PiVPN, you wouldn't need to edit wireguard files manually - it has a neat CLI tool that allows you to administrate your clients more conveniently.

You should consider to consult PiVPN support for further assistance.

[Icona]

Yes, I added the peer using the CLI tool, that wasn’t an issue at all. Issue is that I don’t get any DNS resolution after adding the peer. I’ve been coming to this forum for MANY years, before u were ever around, and since back then, and even as we speak there’s dozens of topics that are about docker, unbound, and other topics that aren’t directly related to pihole. There’s literally a subtopic under help specifically labeled ‘pivpn’, but it’s not actively discussed here?
Whatever floats your boat man. If it makes u feel better, go ahead and delete the post, not going through a pissing contest with basement dwellers.