DNS=144.76.186.21 Domains=luv.asn.au If you add the above 2 lines to the end of /etc/systemd/resolved.conf (or put them in a separate file in the /etc/systemd/resolved.conf.d/ directory) and run "sudo systemctl restart systemd-resolved.service" you will have a separate DNS configuration for the luv.asn.au domain. Note that you can't have multiple separate DNS servers for different domains using the above, so this won't give what you want if you already have a private DNS server. After setting up the domain the command resolvectl should give output like the following: Global Protocols: +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub DNS Servers: 144.76.186.21 DNS Domain: luv.asn.au Link 2 (mb) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/ unsupported Default Route: no Link 3 (wifi) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/ unsupported DNS Servers: 8.8.8.8 DNS Domain: coker.com.au Default Route: yes This shows that the "Default Route" for DNS is 8.8.8.8 while the route for luv.asn.au is 144.76.186.21 This will allow it to keep working for you until we get the domain renewed. NB Make sure you remove this after the renewal. The resolvectl command is supposed to be able to set this and I have done it in the past, but I can't work it out from the man page and the google hits haven't turned up anything useful. Anyone know how to use resolvectl to do this? Before anyone says "read the source", I have read quite a bit of systemd source and it is not easy for outsiders to understand. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
On Thursday, 2 July 2026 13:39:31 AEST Russell Coker wrote:
DNS=144.76.186.21 Domains=luv.asn.au
If you add the above 2 lines to the end of /etc/systemd/resolved.conf (or put them in a separate file in the /etc/systemd/resolved.conf.d/ directory) and run "sudo systemctl restart systemd-resolved.service" you will have a separate DNS configuration for the luv.asn.au domain.
Last Modified: 2026-07-02T03:35:42Z Status: serverRenewProhibited https://identitydigital.au/whois-status-codes#serverRenewProhibited As of 1:35PM Victorian time the domain was renewed. Some of the nodes for the 8.8.8.8 service are still not resolving it while some already have the updated data. Probably that will be the case for a lot of big DNS servers, but I expect that it will all be working in 20 minutes or so. So you can delete such custom configuration in your DNS setup.
The resolvectl command is supposed to be able to set this and I have done it in the past, but I can't work it out from the man page and the google hits haven't turned up anything useful. Anyone know how to use resolvectl to do this? Before anyone says "read the source", I have read quite a bit of systemd source and it is not easy for outsiders to understand.
It would still be good to solve this technical problem. This should be easy to do! I really should write more blog posts of the "here's 2 lines of shell script that took me a week to work out" genre because I have solved this in the past. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
On Thu, 2 Jul 2026 at 13:57, Russell Coker via luv-main <luv-main@luv.asn.au> wrote:
On Thursday, 2 July 2026 13:39:31 AEST Russell Coker wrote:
DNS=144.76.186.21 Domains=luv.asn.au
If you add the above 2 lines to the end of /etc/systemd/resolved.conf (or put them in a separate file in the /etc/systemd/resolved.conf.d/ directory) and run "sudo systemctl restart systemd-resolved.service" you will have a separate DNS configuration for the luv.asn.au domain.
Last Modified: 2026-07-02T03:35:42Z Status: serverRenewProhibited https://identitydigital.au/whois-status-codes#serverRenewProhibited
As of 1:35PM Victorian time the domain was renewed. Some of the nodes for the 8.8.8.8 service are still not resolving it while some already have the updated data. Probably that will be the case for a lot of big DNS servers, but I expect that it will all be working in 20 minutes or so.
It's resolving for me but looks like the WP instance is not configured, returning this... <?php /** * Front to the WordPress application. This file doesn't do anything, but loads * wp-blog-header.php which does and tells WordPress to load the theme. * * @package WordPress */ /** * Tells WordPress to load the WordPress theme and output it. * * @var bool */ define( 'WP_USE_THEMES', true ); /** Loads the WordPress Environment and Template */ require __DIR__ . '/wp-blog-header.php'; -- Colin Fee tfeccles@gmail.com
On Thursday, 2 July 2026 13:59:41 AEST Colin Fee via linux-aus wrote:
It's resolving for me but looks like the WP instance is not configured, returning this...
Yes that's a separate issue. The main web site was not functioning when I looked at it yesterday, I changed a bunch of things and ran out of time/ eneregy with it in that state. https://lists.luv.asn.au/mailman3/hyperkitty/list/luv-main@luv.asn.au/latest The list archives are working fine. I am not a fan of the new Mailman interface, but upstream changing the interface is something we have to deal with. There are many things that Mailman developers have done that I don't like, Phil did really great work just getting it going. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
participants (2)
-
Colin Fee -
Russell Coker