social.lol

0 posts0 participants0 posts today

Paco Hope #resistI realized that I was spending 50¢ every month for 7 Route53 hosted zones at AWS, when I really don't need to do that for some of them. I'm using <code>name.com</code> as my registrar, and they'll do basic <a href="https://infosec.exchange/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNS</a> service for free as a part of that.I didn't want to spend an hour clicking and copy/pasting DNS records, so like any good geek I spent about 6 hours writing a script to do it for me. 😃 It's a bit of a specialized need. If you're not hosted in <a href="https://infosec.exchange/tags/Route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Route53</a> and not looking to go to <code>name.com</code>, this is not useful to you at all, except as a curiosity of how badly I write python.But if (a) you're cheap like me, and (b) you've made the same choices as me, this script will save you some time.<a href="https://git.paco.to/pacohope/route53-namecom-dns" rel="nofollow noopener noreferrer" target="_blank">route53-namecom-dns</a> <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a> <a href="https://infosec.exchange/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a>

Paco Hope #resistThe punchline on my <a href="https://infosec.exchange/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNS</a> reconfiguration is that nothing went wrong because I didn’t actually make any changes that took effect. I do a weird config to have reliable DNS: I have a hidden master that uses dnsmadeeasy as the public servers. They answer authoritatively but they’re getting records from my <a href="https://infosec.exchange/tags/powerdns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#powerdns</a> server.Well, one problem I have is using CDNs at the apex zone. I use <a href="https://infosec.exchange/tags/AWS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AWS</a> <a href="https://infosec.exchange/tags/cloudfront" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cloudfront</a> as my <a href="https://infosec.exchange/tags/CDN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CDN</a>. This is fine when you use <a href="https://infosec.exchange/tags/Route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Route53</a> as your DNS. They can put alias records in at the apex. But it doesn’t work with dnsmadeeasy secondary zones. The way I run them. Name dot com is my registrar. They can do alias records. So I think they also do DNS for free. I’m going to migrate my Route53 zones to the free DNS instead of paying $0.50 per zone per month. All this effort will save me about $6.50/month. <a href="https://infosec.exchange/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a>

Adam ♿A question to <a href="https://aus.social/tags/AWS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AWS</a> <a href="https://aus.social/tags/Route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Route53</a> <a href="https://aus.social/tags/CloudWatch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudWatch</a> experts:I have a <a href="https://aus.social/tags/Route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Route53</a> public zone sending logs to a <a href="https://aus.social/tags/Route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Route53</a> group - why isn't case in the incoming queries preserved?(if someone queries AAA.test.voltagex.org the log will show aaa.test.voltagex.org)

Brian LeRoux 💚pleasantly surprised how easy domain transferring is between <a href="https://indieweb.social/tags/aws" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aws</a> <a href="https://indieweb.social/tags/route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#route53</a> accounts

Jan ☕🎼🎹☁️🏋️‍♂️<a href="https://fedi.kcore.org/tags/aws" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aws</a> just introduced <a href="https://fedi.kcore.org/tags/Route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Route53</a> <a href="https://fedi.kcore.org/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNS</a> profiles. Gimme gimme! <a href="https://aws.amazon.com/about-aws/whats-new/2024/04/amazon-route-53-profiles/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://aws.amazon.com/about-aws/whats-new/2024/04/amazon-route-53-profiles/</a>

Steve Castano<a href="https://mastodon.social/@lucas3d" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@lucas3d</a> for sure keep an eye on it… it’s specifically my wildcard certs that don’t renew properly. My single sites renew with no problem as soon as they are within the 30 day renewal period, but my <a href="https://mastodon.stevex.online/tags/AWS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AWS</a> <a href="https://mastodon.stevex.online/tags/route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#route53</a> and <a href="https://mastodon.stevex.online/tags/PowerDNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PowerDNS</a> ones with the DNS challenge tend to fail repeatedly. Just to cover yourself, a good uptime monitor with cert expiration is what catches mine… I use Uptime Kuma for that: <a href="https://github.com/louislam/uptime-kuma" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/louislam/uptime-kuma</a> (great to run under docker)

CFN UpdatesNew AWS::Route53::RecordSet GeoProximityLocationUse the AWS::Route53::RecordSet GeoProximityLocation property to specify a geoproximity resource recordset. <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-route53-recordset-geoproximitylocation.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-route53-recordset-geoproximitylocation.html</a> <a href="https://awscommunity.social/tags/route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#route53</a> <a href="https://awscommunity.social/tags/cloudformation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cloudformation</a>

Jon "The Nice Guy" SpriggsUsing <a href="https://toot.io/tags/NetworkFirewall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetworkFirewall</a> and <a href="https://toot.io/tags/Route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Route53</a> <a href="https://toot.io/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNS</a> <a href="https://toot.io/tags/Firewall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Firewall</a> to protect a private subnet’s egress traffic in <a href="https://toot.io/tags/AWS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AWS</a> <a href="https://jon.sprig.gs/blog/post/2760" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://jon.sprig.gs/blog/post/2760</a>

CFN UpdatesNew AWS::Route53::RecordSetGroup GeoProximityLocationUse the AWS::Route53::RecordSetGroup GeoProximityLocation property to specify croperty to specify a geoproximity resource recordset. <a href="https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-route53-recordsetgroup-geoproximitylocation.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-route53-recordsetgroup-geoproximitylocation.html</a> <a href="https://awscommunity.social/tags/route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#route53</a> <a href="https://awscommunity.social/tags/cloudformation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cloudformation</a>

CFN UpdatesNew AWS::Route53::RecordSet GeoProximityLocationUse the AWS::Route53::RecordSet GeoProximityLocation property to specify a geoproximity resource recordset. <a href="https://docs.aws.amazon.com/aws-properties-route53-recordset-geoproximitylocation.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://docs.aws.amazon.com/aws-properties-route53-recordset-geoproximitylocation.html</a> <a href="https://awscommunity.social/tags/route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#route53</a> <a href="https://awscommunity.social/tags/cloudformation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cloudformation</a>

Trusty🚨 Introducing a single pane of glass for domains, DNS, and more! 🚨Take control of all your domains, DNS, and SSL certificates across registrars and providers from a single pane of glass.With DNSimple's NEW Domain Control Plane, you can • Add, edit, or remove DNS records. • Register, transfer, or renew domain names. • Request and deploy SSL certificates. • And much much more. Visit 👉<a href="https://blog.dnsimple.com/2023/12/introducing-domain-control-plane/?utm_source=mastodon&utm_medium=social&utm_campaign=DCP" rel="nofollow noopener noreferrer" target="_blank">https://blog.dnsimple.com/2023/12/introducing-domain-control-plane/?utm_source=mastodon&utm_medium=social&utm_campaign=DCP</a><a href="https://dnsimple.social/tags/dns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dns</a> <a href="https://dnsimple.social/tags/sslcertificate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sslcertificate</a> <a href="https://dnsimple.social/tags/domains" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#domains</a> <a href="https://dnsimple.social/tags/domainregistration" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#domainregistration</a> <a href="https://dnsimple.social/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devops</a> <a href="https://dnsimple.social/tags/coredns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coredns</a> <a href="https://dnsimple.social/tags/aws" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aws</a> <a href="https://dnsimple.social/tags/route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#route53</a>

TrustyManaging multiple AWS accounts? Experiencing DNS or domain sprawl? 😓 Get a clean, simple overview of all your domains and DNS in one place 😉. Manage your Route53 zones in DNSimple with our Domain Control Plane 👉 <a href="https://blog.dnsimple.com/2023/06/manage-aws-routes-in-dnsimple/" rel="nofollow noopener noreferrer" target="_blank">https://blog.dnsimple.com/2023/06/manage-aws-routes-in-dnsimple/</a> <a href="https://dnsimple.social/tags/aws" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aws</a> <a href="https://dnsimple.social/tags/route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#route53</a> <a href="https://dnsimple.social/tags/domains" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#domains</a> <a href="https://dnsimple.social/tags/dns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dns</a>

John Manoogian IIII know folks sing the praises of <a href="https://trunk.lol/tags/porkbun" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#porkbun</a> as a <a href="https://trunk.lol/tags/dns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dns</a> service provider, but the <a href="https://trunk.lol/tags/UI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UI</a> could really use some love. It would be SO EASY to at least exceed the UI quality of AWS <a href="https://trunk.lol/tags/Route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Route53</a>’s dns console, and yet porkbun honestly BARELY meets that low bar. As a customer I would love to see what a dns web ui could look like with a little polish and attention to detail and update to modern ui standards.

Major Hayden 🤠Just to follow up, I moved my domain to AWS Route53 and left it there for a week. The response times got *worse* at Route53!Guess it's time to go back to Porkbun! 🤯<a href="https://social.lol/tags/aws" class="mention hashtag" rel="tag">#aws</a> <a href="https://social.lol/tags/dns" class="mention hashtag" rel="tag">#dns</a> <a href="https://social.lol/tags/route53" class="mention hashtag" rel="tag">#route53</a> <a href="https://social.lol/tags/porkbun" class="mention hashtag" rel="tag">#porkbun</a> 🐷

TrustyYou don’t need complex UI just to manage your DNS zones 😓. Get a clean, simple overview of all your digital assets in one place 🤩. Manage your Route53 zones within DNSimple, read more 👉 <a href="https://blog.dnsimple.com/2023/06/manage-aws-routes-in-dnsimple/?utm_source=mastodon&utm_medium=social&utm_campaign=route53" rel="nofollow noopener noreferrer" target="_blank">https://blog.dnsimple.com/2023/06/manage-aws-routes-in-dnsimple/?utm_source=mastodon&utm_medium=social&utm_campaign=route53</a> <a href="https://dnsimple.social/tags/aws" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aws</a> <a href="https://dnsimple.social/tags/dns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dns</a> <a href="https://dnsimple.social/tags/awsdevops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#awsdevops</a> <a href="https://dnsimple.social/tags/uideveloper" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#uideveloper</a> <a href="https://dnsimple.social/tags/route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#route53</a> <a href="https://dnsimple.social/tags/dev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dev</a>

Stefan Midjich ꙮ҄A Dynamic <a href="https://mastodon.se/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNS</a> <a href="https://mastodon.se/tags/Ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ansible</a> role for <a href="https://mastodon.se/tags/AWS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AWS</a> <a href="https://mastodon.se/tags/Route53" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Route53</a> in case anyone is interested. It's part of my <a href="https://mastodon.se/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> setup.<a href="https://mastodon.se/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#python</a> <a href="https://gitlab.com/stemid-ansible/homelab/-/tree/main/roles/route53-dyndns" rel="nofollow noopener noreferrer" target="_blank">https://gitlab.com/stemid-ansible/homelab/-/tree/main/roles/route53-dyndns</a>

Recent searches

Search options

Administered by:

Server stats:

#Route53