On 27. 06. 22 8:26, Evan Hunt wrote:
On Sun, Jun 26, 2022 at 10:00:08PM -0500, Larry Stone wrote:
I recently moved from 9.16 to 9.18 and just noticed that dig no longer
resolves mDNS queries.
With 9.16:
dig +short @224.0.0.251 -p 5353 hostname.local
192.168.0.82
With 9.18:
dig +short @224.0.0.
On Sun, Jun 26, 2022 at 10:00:08PM -0500, Larry Stone wrote:
> I recently moved from 9.16 to 9.18 and just noticed that dig no longer
> resolves mDNS queries.
>
> With 9.16:
> dig +short @224.0.0.251 -p 5353 hostname.local
> 192.168.0.82
>
> With 9.18:
> dig +short @224.0.0.251 -p 5353 hostname.l
I recently moved from 9.16 to 9.18 and just noticed that dig no longer resolves
mDNS queries.
With 9.16:
dig +short @224.0.0.251 -p 5353 hostname.local
192.168.0.82
With 9.18:
dig +short @224.0.0.251 -p 5353 hostname.local
;; connection timed out; no servers could be reached
I can’t find anythi
On 26-06-2022 23:19, Mark Andrews wrote:
The names of name servers need to follow the rules for hostnames.
i.e. the labels are made up of letters, digits and hyphens (LDH).
That means the name servers can’t live in the zone. There should be
no A or records in the zone.
Similarly there can’t
The names of name servers need to follow the rules for hostnames. i.e. the
labels are made up of letters, digits and hyphens (LDH). That means the name
servers can’t live in the zone. There should be no A or records in the
zone.
Similarly there can’t be MX records as they also are restric
Hello,
I recently ran into "bad [owner] name" errors trying to setup a
'_acme-challenge' subdomain. Yes, this is for Let's Encrypt domain
validation.
I wanted to use the dns-rfc2136 plugin [1], which, as the name suggests,
does dynamic zone updates for the authentication challenge. Since my
6 matches
Mail list logo
