Internet stops after configuring the forwarding and applying the custom DNS settings.
Internet stops after configuring the forwarding and applying the custom DNS settings.
I have a plan to improve my home setup and wanted to easily reach my school printer from there. This way, I won’t have to remember printing materials for teachers every time I arrive. I located an unused Raspberry Pi, installed it, purchased a public IP address from my ISP, and began the process. Everything functioned properly until I hit a roadblock and couldn’t resolve the final step needed to complete this task. Each time I configured port forwarding to the Pi, the internet remained stable, but new connections failed (such as Discord calls or YouTube streams). This issue only disappears when I switch the DNS on my Pi-hole to another provider like Cloudflare. Initially, I suspected Pi-hole might reuse the same port for its services, but after changing the print server’s port multiple times, that wasn’t the case. I also attempted to set up Pi-hole as a DNS resolver for all devices, but it didn’t help. Please note that if my DNS forwarding is directed to Pi-hole, it should receive the response “OK, sent to 1.1.1.1,” which is normal behavior. Router model: Phicomm KE 2P – Sorry if my explanation isn’t clear; I’m not a fluent speaker.
I’d rather be very tired or leave a print server online… that’s a path to being compromised. If you have a Pi, just configure a VPN and connect it to your home network for printing, or try split tunneling. You can also use dynamic DNS (like duckDNS) to link your changing IP with a web address—no extra cost from your ISP. As for the rest, I’m not confident.
The print server is just a front end. I also want to ensure it stays secure without needing a password or token—so it should be saved. Even if I can’t figure out the details, I need it to work. I’d like a private server where I can upload files safely, so I don’t lose anything if my laptop fails. There are other settings that need public IPs, which is why I’m trying to learn more about port forwarding, though it’s tough because I’m still figuring it out.
Using duckDNS lets you control your dynamic IP address freely and it updates automatically. You can register it under MartinRusnak.duckDNS.com (though I’m not sure if that’s the exact domain duckDNS uses, but the idea remains) and it will always route traffic to your public IP. Regarding passwords and tokens, I’m certain print servers are commonly vulnerable. They’re designed for internal use only. Anything exposed online should be protected with a VPN or SSL tunnel unless it’s intentionally public. If you have access to a Raspberry Pi, consider setting up WireGuard. Configure the VPN, open the necessary ports, and you’ll appear on your home network when connected. This approach secures your setup, shrinks potential threats, and gives you the features you need. You could also create an SMB share on your RPi using an external drive, and access it securely through the VPN just like at your local LAN.
Consider building a web server to upload files for printing. It should include login protection. For connecting to other services like web servers or VPNs, you'll need the port forwarding details. Could you send a screenshot of your router's port forward configuration?
Thanks for the guidance on the print server. I’ll consider it. Here’s the screen you mentioned.
The configuration appears fine. I’d suggest permitting only TCP or UDP based on the requirements. Which print server are you working with? Did you follow any specific tutorials? Also, how many devices are connected and what is their usage like? Check your routers’ specifications—you might need to adjust capacity accordingly.
Ahh, mate sorry, But I think that you are not understanding the problem. No offence, I appreciate your advice, but my current problem is that I can't use my Pi-hole as DNS since it just decides to cut off my connection to WAN whenever I set DNS to any local IP. My local DNS is a Pi-hole , an open-source project, with the goal to make managing LAN traffic easier and block unwanted websites. In most cases mainly adverts, but in my case also NSFW sites or sites that could potentially scam my parents. The problem is not that I can't connect to my print server, it is with the connection of my house to the internet. My house cannot communicate with anything outside my LAN. I answer you so I don't offend you, but I don't think we're moving to the right deriction. I have got total of 17 devices connected to my network. Only 4 of them require communication to the internet at high speeds - My PC, two TVs, and my smartphone. Everyone of them, exept for phone, is connected with RJ-45 (aka. Twisted pair networking cable, LAN cable).
I get what you're going through, I’m trying to figure out why Pi-hole isn’t responding to DNS queries while the print server is active. It seems like changing your device’s DNS might help if the print server is running. If the print server isn’t up, does the problem persist? If it does, we can look into other possibilities. I assume Pi-hole is installed on the same system as the print server. What upstream DNS does it rely on? Also, keep in mind that all internet-connected devices need to connect through the router. With heavy usage, the router might struggle. In this case, the print server could be interfering or port forwarding might be causing issues.