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

[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: Aug 1, 2024

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!

 

[einhuman197]

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: Aug 1, 2024

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.