Just so I find it again when I run across the same problem in the future:

I wanted to log in to one of my servers and couldn’t access it, because I couldn’t resolve the name from one specific domain. All other domains worked fine.

So let’s head over to the DNS server and check what we can do. I’m running BIND, and it ships with two tools, named-checkconf and named-checkzone. As the name implies named-checkconf checks the overall configuration, named-checkzone single zone. There is also an option -z for named-checkconf that checks all the primary zones found in the configuration.

Some shameless advertising:

If you need some help with IPv6, DNS, Linux, Automation and related stuff feel free to contact me. I’m available for about two days a week, remote preferred.

• CLAT in Linux Networkmanager
• DNS delegation
• jc - Convert command output to json
• Stratoshark - Analyse syscalls
• curl from start to end
• Security Bingo
• Linux Routing Fundamentals
• Packet where are you
• nftable-tracer

You want to make a presentation, write a blog post or document your brand-new software. What do you use as domain-names, IP addresses and AS numbers? If you are documenting your systems or a setup you build for a customer the question is easy to answer: It’s best to use the actual data. But if you are writing a more generic documentation there are some reserved domain names, IP prefixes and AS numbers.