OK. That was weird.

$ nslookup srv01
Server: 192.168.1.10
Address: 192.168.1.10#53

Non-authoritative answer:
Name: srv01.fritz.box
Address: 192.168.1.38

But

$ ping srv01
ping: cannot resolve srv01: Unknown host

And after an hour it simply works again without anything changed.

#ItsAlwaysDNS :)

Microsoft learned today that #ItsAlwaysDNS. #AzureOutage

UPDATE: services are recovering, rollback succeeded

Last week AWS, now Azure.

#ItsAlwaysDNS :)

"[...] we began experiencing DNS issues resulting in availability degradation of some services [...]"

UPDATE: They have now changed the wording to "we began experiencing Azure Front Door issues resulting in a loss of availability of some services" and the impact is now CRITICAL — Azure Network Availability Issues on a global level.

https://azure.status.microsoft/en-gb/status

Alt...

Critical Azure Portal Access Issues Starting at approximately 16:00 UTC, we began experiencing DNS issues resulting in availability degradation of some services. Customers may experience issues accessing the Azure Portal. We have taken action that is expected to address the portal access issues here shortly. We are actively investigating the underlying issue and additional mitigation actions. More information will be provided within 60 minutes or sooner. This message was last updated at 16:35 UTC on 29 October 2025

@jpmens The root cause? https://x.com/ndbroadbent/status/1980172049147658445

#itsAlwaysDNS

We should abandon #DNS and just memorise IP addresses, as we did in ye olden days!1!!

#SarcasmButOnlyHalf #AWS #ItsAlwaysDNS

Amazon people frantically editing /etc/hosts files everywhere to get DynamoDB working again ;) Time for a coffee.

https://health.aws.amazon.com/health/status

#ItsAlwaysDNS #AWS #DynamoDB #USEAST1

No, I won't try to debug a perl script that does weird things. I'll just write the reverse lookup zone by hand.

#ItsAlwaysDNS

#ItsAlwaysDNS Finally learning IPv6, a thing I tried to avoid for the longest time. All my servers are reachable via IPv6, I know how to do that, but now I am learning to set up IPv6 in my home(lab) network and wrapping my head around concepts like ULAs (Unique Local Addresses, that don't route to/from the internet), prefixes I get from my ISP and how all of that translates to DNS entries on my BIND9. Mistakes will be made.

1/4

#SelfHost #Homelab #IPv6 #DNS

#ItsAlwaysDNS I took the plunge. Configured my Fritz Box to hand out my new DNS server to all DHCP devices. So now DNS requests go first to my BIND9, which resolves homelab.jhw. If it can't answer, it forwards to the Fritz Box, who takes care of the local fritz.box domain. And if that doesn't work it goes out to the internet. Seems to work :) I can now reach my homelab machines under their homelab.jhw name and with a valid certificate. Yay! Updated the gist too.

3/3

#SelfHost #DNS #Homelab

Alt...

A browser tab on my laptop showing that it has connected to one of my servers in my homelab with the correct hostname hl01.homelab.jhw and with a valid certificate coming from my own certificate authority.

Alt...

Two dns lookups in my home network, showing how my DNS setup correctly resolves two different domains on the same network. % nslookup jhwfritz.fritz.box Server: 192.168.1.10 Address: 192.168.1.10#53 Non-authoritative answer: Name: jhwfritz.fritz.box Address: 192.168.1.254 % nslookup ca.homelab.jhw Server: 192.168.1.10 Address: 192.168.1.10#53 ca.homelab.jhw canonical name = inf01.homelab.jhw. Name: inf01.homelab.jhw Address: 192.168.1.10

#ItsAlwaysDNS This is rather advanced stuff, but I brain dumped how I configured my Bind DNS server for my homelab that allows all my servers, containers etc to resolve local and global names. Just the config, no detailed explanations. Might do that as a blog post. Should I?

https://codeberg.org/jwildeboer/gists/src/branch/main/2025/20250826DNSHomelabBind9.md

UPDATE: Blog post done, see https://social.wildeboer.net/@jwildeboer/115113695729233240

1/3

#SelfHost #Homelab #DNS

#ItsAlwaysDNS and its BIND9 corollary "Did you increment the serial in the zone file?" ;)

#ItsAlwaysDNS but I managed to get my own BIND9 name server up and running on the Raspberry 4 in my homelab. So I can now continue with setting up a new Certificate Authority (CA) as container. (please refrain from replying with "use dnsmasq!" or other solutions. I know what I am doing and I am stubborn. I'm a BIND9 guy. Period. :)

#SelfHost #Homelab

Alt...

A working DNS lookup on a CNAME entry in homelab, served by my own DNS server.