All, I am testing a AWS server that runs the DNS and HTTP services for my node. NTP (kb3vwg-001.ampr.org/44.60.44.1) was not moved. Please verify: ~ AMPR DNS (44.60.44.3)  - OPEN ACCESS for AMPRNet hosts, 44 hosts can also AXFR 44.in-addr.arpa. and ampr.org - **if you accessed DNS via your WAN IP and it's now fails, let me know off thread about why and/or reconfigure to use your AMPRNet IP for inquires** - **If you used HTTP on this address, it now fails** --- ~ AMPR HTTP (44.60.44.10): - http://whatismyip.ampr.org - you will only receive your valid 44 SRC IP on AMPRNet, all other IPs receive the non-Internet-reachable 44.60.44.254 - http://speedtest.ampr.org - currently Error 302 redirects to https://speedtest.org/ - Main landing (http://kb3vwg-010.ampr.org / http://44.60.44.10) - amprdocs and tools pages should be visible here if you're on AMPRNet - **The 44-Trace and Ping tools to 44 IPs ONLY should work as intended - please message me off thread if not** - other IPs (and 44.0.0.1/32) use the AWS interface now - **Since this server is now hosted...I am able to add my device as an official Slave DNS of AMPRNet on its real interface...if you all desire (and it's approved)** - I'd like to test transfer on a temporary basis before we make it a go...I do pay for if it spikes, LOL --- ~ WAN HTTP (<IP>): -  http://kb3vwg.ampr.org (WAN HTTP) - is no longer CMS-based - Main landing (http://<IP>/)  - currently Error 302 redirects to https://speedtest.org/ (HINT: you can nslookup kb3vwg.ampr.org for the current WAN IP) NOTE: if you accessed NTP via your WAN IP, this may change in the future. Please migrate to using AMPRNet SRC IPs access to ALL AMPRNet services [on the KB3VWG node]. (This temp test may lead to proof-of-concept for a FREE/donated permanent site [for more services/CPUs] for VMs.) 73, - Lynwood KB3VWG