% title 'News'; % layout 'swagg';

News

+--------------------------+

6/25/2020 - Major Downtime Coming

+--------------------------+

I am going to be moving equipment this weekend (6/26/2020 to 6/28/2020) so there may be a full day or two of downtime while I piece everything together. In the future I'm going to move the MOTD and this little news section to another server because this message kind of defeats the purpose (didn't help I posted it at the last minute WHOOPS)

+--------------------------+

1/17/2020 - New Domain Name

+--------------------------+

I purchased the swagg.net domain name last year but never go around to cutting over from the old one. As with the move from swagg.ddns.net, I'm going to hold onto swagg.cc to serve redirects but eventually I'll be letting it go as swagg.cc actually costs me money

+--------------------------+

7/26/2019 - Now serving HTTPS

+--------------------------+

I got bored and changed stuff and now there's HTTPS

+--------------------------+

7/17/2019 - New IP addresses

+--------------------------+

Due to me physically moving my server (and everything) to my new place in Northern VA, there was some downtime (2 days) and SwaggNet now has all new IP addresses. I think it's done now but there may be some more downtime at night during the weekend as I have to clean up my cabling as things got a bit spaghettified during the move and I haven't had the time to unravel it all.

+--------------------------+

5/13/2019 - New domain name (and IPv6!!)

+--------------------------+

I've been quietly playing around with IPv6 for some time and finally felt comfortable going "global" with it, however the old domain name (swagg.ddns.net) was a free Dynamic DNS name and thus was not configurable as an AAAA (IPv6) record. Therefore swagg.cc is now the new domain name for SwaggNet and swagg.ddns.net has be reconfigured to simply point to swagg.cc and will stay that way as long as I can hold on to that name. swagg.cc should now resolve to IPv4 or IPv6 and if you're curious or want to test your own IPv6 configuration, I've also created ipv6.swagg.cc which will only be used for IPv6 records so using ipv6.swagg.cc should essentially force an IPv6 session if everything's been set up correctly.