Project New Public Pegascape DNS - Replacement for the Public EOL DNS by noahc3

  • Thread starter Thread starter einhuman197
  • Start date Start date
  • Views Views 13,668
  • Replies Replies 38
  • Likes Likes 12
ok, apparently I do not have the tab installed within Pegascape. So, I am not sure what I need to do? Looks like I only have Caffeine and HBL tabs within Pegascape.
Post automatically merged:

I went back through all my backups and logically reasoned I could have a corrupt Atmosphere file that is preventing me from loading exploit. Since the last time I had to restore my Switch was through a power loss and battery not charging. I deleted the switch and atmoshere folders and re-added 1.7.0 Atmosphere back onto the SD card. Bam, the exploit worked this time. Thanks for the guides!
 
Last edited by Luc20100,
ok, apparently I do not have the tab installed within Pegascape. So, I am not sure what I need to do? Looks like I only have Caffeine and HBL tabs within Pegascape.
Post automatically merged:

I went back through all my backups and logically reasoned I could have a corrupt Atmosphere file that is preventing me from loading exploit. Since the last time I had to restore my Switch was through a power loss and battery not charging. I deleted the switch and atmoshere folders and re-added 1.7.0 Atmosphere back onto the SD card. Bam, the exploit worked this time. Thanks for the guides!
Hey, sorry for the late reply! Glad it works for you now!

I have no ICMP to your DNS
Regarding the fact that you weren't able to Ping the Server: Good point! It's the default network configuration of Oracle Cloud Machines to drop basically all ICMP Traffic, that includes the Echo Reply/Ping. I forgot to change that when configuring the machine. I enabled all ICMPv4 Traffic now (@ Nintendo pls don't DDoS), feel free testing pinging it! It works on my side.

Just as a side note: I didn't enable ICMPv6 or IPv6 on the machine. While Oracle supports Full Dual Stack and it'd be a very good thing for any public Service on the Internet to have IPv6 nowadays, sadly the Switch isn't able to handle IPv6 DNS Servers, it's stuck with Legacy IP. So configuring Dual Stack for the entire machine just doesn't make sense, because the Switch can't handle it.

We'll see what we can do regarding public hosting once IPv4 Flag Day comes around, maybe some NAT46 magic in the internal network will be needed once ISPs stop providing Legacy IP addresses to customers. The entire npm project might need some patches, I haven't checked if it works with IPv6 Requests. But I think that'll only be a problem in several years down the road.
 
any build of the fakenews injector works on new fw/atm 18 or 19.00? i mean, i want to launch it only to unninstal pegascape, i've got a switch with one installed and can't get rid of it without formating /restoring the nand.
 
any build of the fakenews injector works on new fw/atm 18 or 19.00? i mean, i want to launch it only to unninstal pegascape, i've got a switch with one installed and can't get rid of it without formating /restoring the nand.

If your OFW is above 4.1.0 then it won't work.
 
  • Like
Reactions: almmiron
Hi there!
Is it still up?
Hey, always has been! Health Logs looks clean, and I just confirmed it's working with my Switch. Does is still not work for you?

any build of the fakenews injector works on new fw/atm 18 or 19.00? i mean, i want to launch it only to unninstal pegascape, i've got a switch with one installed and can't get rid of it without formating /restoring the nand.
I think you need to build it from the sources. There were plenty of Patches from Nintendo over the years that change access with homebrew. You have the Firmware 19 on emuNAND, right? On SysNAND you obviously need to stay on 4.1.0 max. If you're above that, you are out of luck without a modchip.
 
Last edited by einhuman197,
Hey, always has been! Health Logs looks clean, and I just confirmed it's working with my Switch. Does is still not work for you?


I think you need to build it from the sources. There were plenty of Patches from Nintendo over the years that change access with homebrew. You have the Firmware 19 on emuNAND, right? On SysNAND you obviously need to stay on 4.1.0 max. If you're above that, you are out of luck without a modchip.
I tested it right now and it appears to be working!

Thank you very much! :D
 
Last edited by DetonaHard,
  • Like
Reactions: einhuman197
Hello, I used your DNS and I hosted PegaScape on my PC too. After the caffeine notification shows up, I tap the text field and press the power button, but nothing happens. What could it be? Switch firmware is 4.1.0.

Thanks.

update: I just did a fresh atmos and hekate install in my SD. It works fine! ;)
 
Last edited by AcIdPort,
  • Like
Reactions: einhuman197
First of all Thank you, I needed to update the DNS and found yours.
Second I have not clear the difference between your in applet mode and the one in Wifi Auth Mode, It doesn´t change nothing right? connect to the wifi, launch pegascape and Emunand.
And last there is any guide/recomendation to host my own dns with theses requirements using a server ubuntu/debian/proxmox what is your recomendation.
Thanks again.
 
First of all Thank you, I needed to update the DNS and found yours.
Second I have not clear the difference between your in applet mode and the one in Wifi Auth Mode, It doesn´t change nothing right? connect to the wifi, launch pegascape and Emunand.
And last there is any guide/recomendation to host my own dns with theses requirements using a server ubuntu/debian/proxmox what is your recomendation.
Thanks again.
Choosing between the Applet Mode and WiFi Auth Mode depends on how you used to launch PegaScape. If you have the "Launch Pegascape" News injected within your News Applet and you launch it that way, the Applet Mode IP is the DNS for you. If you launch PegaScape through the WiFi Authentication Prompt, then you need to use the WiFi Auth DNS.

I had good luck on my VPS with Ubuntu 22.04 LTS. It should work with any Debian Based Distribution just fine. Just keep in mind that while running PegaScape, the DNS of your machine will not work, as Port 53 usually used for DNS Requests is occupied by your machine operating a DNS Server itself. Also because it uses ancient node.js it might be an avoidable security risk on existing systems. So if you want a PegaScape DNS in your network, you should make a dedicated vm. You barely need any resources though, you should be fine with Single Core, 1GB RAM or even 512MB RAM, maybe 10GB of Disk Space (Ubuntu 22.04 LTS Minimal needs around 8.5GB, the node.js and Files from the Repo only need a few MB each).
 
Choosing between the Applet Mode and WiFi Auth Mode depends on how you used to launch PegaScape. If you have the "Launch Pegascape" News injected within your News Applet and you launch it that way, the Applet Mode IP is the DNS for you. If you launch PegaScape through the WiFi Authentication Prompt, then you need to use the WiFi Auth DNS.

I had good luck on my VPS with Ubuntu 22.04 LTS. It should work with any Debian Based Distribution just fine. Just keep in mind that while running PegaScape, the DNS of your machine will not work, as Port 53 usually used for DNS Requests is occupied by your machine operating a DNS Server itself. Also because it uses ancient node.js it might be an avoidable security risk on existing systems. So if you want a PegaScape DNS in your network, you should make a dedicated vm. You barely need any resources though, you should be fine with Single Core, 1GB RAM or even 512MB RAM, maybe 10GB of Disk Space (Ubuntu 22.04 LTS Minimal needs around 8.5GB, the node.js and Files from the Repo only need a few MB each).
EDIT:

I had a similar issue to a previous user: when launching Pegascape with Caffeine and needing to press the power button, nothing happened. I had forgotten to downgrade hbmenu to the April 2019 version, which I believe corresponds to Atmosphère 0.8.8. With that, everything works fine.
 
Last edited by hunter_x,
  • Like
Reactions: einhuman197
Hello everyone!

I’ve repeatedly tried to launch Caffeine with Pegascape — until last year, everything worked without any issues.

After the Pegascape DNS servers were shut down, I switched to running everything locally, but for the past few months it has stopped working even that way.

I also tried using @einhuman197 DNS, but it doesn’t work either.

In both cases, Pegascape starts, I launch Caffeine, then I get to the “wait 3 seconds and press power” pop-up, and when I touch it the Switch crashes…

I always get error 2207-0248, I don’t know what to do.

I’ve tried 2 different Wi-Fi connections and 2 different 4G connections, from 3 different ISPs in total.

Any suggestions? Help!
 
Hello everyone!

I’ve repeatedly tried to launch Caffeine with Pegascape — until last year, everything worked without any issues.

After the Pegascape DNS servers were shut down, I switched to running everything locally, but for the past few months it has stopped working even that way.

I also tried using @einhuman197 DNS, but it doesn’t work either.

In both cases, Pegascape starts, I launch Caffeine, then I get to the “wait 3 seconds and press power” pop-up, and when I touch it the Switch crashes…

I always get error 2207-0248, I don’t know what to do.

I’ve tried 2 different Wi-Fi connections and 2 different 4G connections, from 3 different ISPs in total.

Any suggestions? Help!
Make sure you fully power cycle your switch (press power button for 30s) and try a different SD Card with fresh pegascape files. I made this archive to help another guy a while ago, worked for them with a different problem, test it on a freshly fat32 formatted microSD.

 
Just made an account to express my gratitude, if i had money i'd throw a lot your way holy f*ck thank you. I was selfhosting my own thing but for some reason it stopped working, like I could use node start.js --webapplet just fine, but the thing wouldn't connect to my switch even after being properly configured


You're an angel, bless you, and I pray you're doing great ♠
 
  • Like
Reactions: einhuman197
Just made an account to express my gratitude, if i had money i'd throw a lot your way holy f*ck thank you. I was selfhosting my own thing but for some reason it stopped working, like I could use node start.js --webapplet just fine, but the thing wouldn't connect to my switch even after being properly configured


You're an angel, bless you, and I pray you're doing great ♠
Thanks for your kind words, I'm doing very well! Glad my efforts are helping you and others!

No worries about donations or anything like that; since the server currently runs on free tier I don't have any actual hosting costs. If that'd ever change, I'll move the hosting somewhere cheap; shouldn't be a problem for me to finance it. If you consider donating and ever come across a few spare bucks, please donate them somewhere else instead. I would suggest the Internet Archive and their awesome archiving efforts, they need it more than I do :)
 
Great effort! Just wondering if this still works. I need to update my emunand soon, and I'm afraid being sent back to emunand will rob me of ever being able to access it again. Can't remember how I did it a year and a half ago.
 
  • Like
Reactions: einhuman197
Hello, I was able to boot normally a couple of months ago with your dns but today I couldn't. It stays on a black screen after I press power, any Ideas? I though it could have been an issue inside my sd but I already updated everything, I don't know what to do.

Edit: Nevermind, I scouted the post and found your clean pegascape files, bro I'd suck y*** f**** **** lmao, thanks again for everything.
 
Last edited by SanzoArts,

Site & Scene News

New Hot Discussed User Submitted