From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: DANE-Record for www.ipfire.org missing
Date: Sat, 11 Nov 2017 15:47:01 +0000 [thread overview]
Message-ID: <49C6D947-AA40-4A3A-8DBE-9F74B0713194@ipfire.org> (raw)
In-Reply-To: <20171111163605.1e18520e.peter.mueller@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1937 bytes --]
We usually don’t have that long TTLs and I actually found it quite likely that I could have forgotten one...
> On 11 Nov 2017, at 3:36 pm, Peter Müller <peter.mueller(a)link38.eu> wrote:
>
> Hello Michael,
>
>> Hi,
>>
>> I get this:
>>
>> [ms(a)hughes ~]$ dig TLSA _443._tcp.ipfire.org
>>
>> ; <<>> DiG 9.11.1-P3-RedHat-9.11.1-2.P3.fc26 <<>> TLSA _443._tcp.ipfire.org
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4259
>> ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
>>
>> ;; OPT PSEUDOSECTION:
>> ; EDNS: version: 0, flags:; udp: 4096
>> ;; QUESTION SECTION:
>> ;_443._tcp.ipfire.org. IN TLSA
>>
>> ;; ANSWER SECTION:
>> _443._tcp.ipfire.org. 21600 IN CNAME _letsencrypt.certs.ipfire.org.
>> _letsencrypt.certs.ipfire.org. 21600 IN TLSA 2 1 1 60B87575447DCBA2A36B7D11AC09FB24A9DB406FEE12D2CC90180517 616E8A18
>>
>> ;; Query time: 66 msec
>> ;; SERVER: 192.168.191.1#53(192.168.191.1)
>> ;; WHEN: Fri Nov 10 22:18:02 GMT 2017
>> ;; MSG SIZE rcvd: 129
>>
>> What is it you are getting?
> The same now. Not sure what caused the delay here. Anyway, it works. :-)
>
> Best regards,
> Peter Müller
>>
>> If you want to avoid the caches, just query
>> ns[123].lightningwirelabs.com.
>>
>> -Michael
>>
>>> On Fri, 2017-11-10 at 20:59 +0100, Peter Müller wrote:
>>> Hello Michael,
>>>
>>> during some tests, I noticed that the DANE record for
>>> www.ipfire.org is still missing. In the first place, I
>>> thought this was because of some DNS reply caching, but
>>> it isn't.
>>>
>>> Just for the record, should be an easy change.
>>>
>>> Apart from that all DANE records seem to be present.
>>>
>>> I will deal with the Postfix configuration on IPFire's MX
>>> next week (need to work at the weekend).
>>>
>>> Best regards,
>>> Peter Müller
>
prev parent reply other threads:[~2017-11-11 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 19:59 Peter Müller
2017-11-10 22:19 ` Michael Tremer
2017-11-11 15:36 ` Peter Müller
2017-11-11 15:47 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49C6D947-AA40-4A3A-8DBE-9F74B0713194@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox