Try ping sun.hac.lp1.d4c.nintendo.net from your computer and see if the router does block itWell i blocked sun.hac.lp1.d4c.nintendo.net in my router and it still updated.
Some routers URL filtering function (such as mine) just don't work
Try ping sun.hac.lp1.d4c.nintendo.net from your computer and see if the router does block itWell i blocked sun.hac.lp1.d4c.nintendo.net in my router and it still updated.
What is your router make/model?Try ping sun.hac.lp1.d4c.nintendo.net from your computer and see if the router does block it
Some routers URL filtering function (such as mine) just don't work
I could be wrong but I think there are two receive URLs that @DocAmes1980 brought upIf you want to block everything then here:
NOTE: These URLs are encrypted hence port 443. Some consumer routers do not let you enter a port in your blocking interface you may have to use HTTPS:// instead.
http://aqua.hac.lp1.d4c.nintendo.net:443
http://sun.hac.lp1.d4c.nintendo.net:443
http://receive-lp1.dg.srv.nintendo.net:443
http://bcat-data-lp1.cdn.nintendo.net:443
http://bcat-list-lp1.cdn.nintendo.net:443
http://tagaya.hac.lp1.eshop.nintendo.net:443
http://dauth-lp1.ndas.srv.nintendo.net:443
EDIT: URLs related to eshop, how did google get in there those sneaky buggers!
http://bugyo.hac.lp1.eshop.nintendo.net:443
http://accounts.nintendo.com:443
http://www.google-analytics.com:443
http://ecs-lp1.hac.shop.nintendo.net:443
If you want to just block the nag screen and update server use this one:
http://sun.hac.lp1.d4c.nintendo.net:443
Disclaimer: URLs are subject to change, I will not be held responsible if nintendo suddenly starts using, for eg. deathstar.hac.lp1.d4c.nintendo.net for updates. Also some of those addresses seem region specific cdn.nintendo.net. Your mileage may vary.
How come you leave tagaya url unblocked? Which is that for exactly.I'm not sure that's how it works on the Switch. I've been using a DNS emulator to resolve "sun.hac.lp1.d4c.nintendo.net" to NXDOMAIN for about a week now. I've also been blocking "receive-lp1.dg.srv.nintendo.net" and "receive-lp1.er.srv.nintendo.net" as they appear to be for telemetry and error reporting respectively. I'm not blocking "tagaya.hac.lp1.eshop.nintendo.net". Manually checking for updates fails as well as automatic updates. I'm still on 2.0.0 and have seen no nag screen. Also, game updates work as expected. There is a curiosity though. I didn't pay close attention to traffic before the 2.1.0 update went live but I noticed the Switch checked for updates (attempted to connect to sun.hac.lp1.d4c.nintendo.net) somewhat infrequently. A day after the 2.1.0 update came out I checked traffic and noticed it was attempting to contact "sun.hac.lp1.d4c.nintendo.net" every minute. I wonder if after it fails to contact the update server after X number of days it starts to check every minute. If the Switch was aware of a newer version I'd think I would be presented with the nag screen.
I could be wrong but I think there are two receive URLs that @DocAmes1980 brought up
How come you leave tagaya url unblocked? Which is that for exactly.
I'm piecing together from what everyone here has gathered. Let me know if theres anything else that should be added or fixed.Thanks, the other one was for error reporting, I added it to the list among a bunch of others.
I just added these:I'm piecing together from what everyone here has gathered. Let me know if theres anything else that should be added or fixed.
https://docs.google.com/document/d/1SC9XYH29zdeCm--PVbdTF9WOCJgfNT99dBGDI4oWyj0/edit
I'll add them and credit you too. Thank you sir.I just added these:
http://app-a04.lp1.npns.srv.nintendo.net:443
http://accounts.nintendo.com:443
http://api.accounts.nintendo.com:443
http://e0d67c509fb203858ebcb2fe3f88c2aa.baas.nintendo.com:443
http://consumer.lp1.npns.srv.nintendo.net:443
http://api.accounts.nintendo.com:443
http://beach.hac.lp1.eshop.nintendo.net:443
http://receive-lp1.er.srv.nintendo.net:443 - error reporting
http://superfly.hac.lp1.d4c.nintendo.net:443 - Game updates server
http://atum.hac.lp1.d4c.nintendo.net:443
No, thank you. I do things for the greater good, and I help people because I like to help and problem solve. People don't usually even say "thanks".I'll add them and credit you too. Thank you sir.
I suggest everyone block this one too:
http://receive-lp1.er.srv.nintendo.net:443
Every Time the update server is blocked it phones home and reports the error. No sense giving Ninty anymore info than they need.
Sounds like your router only supports site blocking using keywords. Have you tried just using:On my router's parental controls I cant block the url as http://sun.hac.lp1.d4c.nintendo.net:443 but I can block it as sun.hac.lp1.d4c.nintendo.net:443
Will it still block updates regardless?
Yes I can add it without the port number but would it still block? Thats all I'm concerned with, as long as it works.Sounds like your router only supports site blocking using keywords. Have you tried just using:
sun.hac.lp1.d4c.nintendo.net
Without the http or port #?
Try to ping sun.hac.lp1.d4c.nintendo.net you will see if it is being blocked or not.Yes I can add it without the port number but would it still block? Thats all I'm concerned with, as long as it works.
I never thought of trying that to begin with. You sometimes forget the basics, thank you.Try to ping sun.hac.lp1.d4c.nintendo.net you will see if it is being blocked or not.
Crap router from my ISPWhat is your router make/model?
Be sure your firewall is enabled.Crap router from my ISP
Manufacturer:FiberHome;
ProductClass:AN5506-04-F
Be sure your firewall is enabled.
Then on the filter screen click enable, make sure blacklist is selected, then click apply.
Click add, then enter this:
sun.hac.lp1.d4c.nintendo.net