public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: 81.3.27.54 => rDNS => Reverse lookup failed
Date: Sat, 14 Jul 2018 18:27:23 +0200	[thread overview]
Message-ID: <08bf349d-8d7c-4871-fccf-eb4cd50e5c06@ipfire.org> (raw)
In-Reply-To: <547390ae2283fec6cd1bd7ef43bd7e7a946a226d.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 728 bytes --]

On 14.07.2018 15:34, Michael Tremer wrote:
> On Sat, 2018-07-14 at 12:29 +0200, Matthias Fischer wrote:
>> Hi!
>> 
>> Since both DNS.WATCH-Servers are unavailable since today...
> 
> LOL

Second time this year. *Sigh*

>> => https://forum.ipfire.org/viewtopic.php?f=27&t=20253&p=117259#p117259
>> 
>> ...I switched to Lightning Wire Labs (81.3.27.54).
>> 
>> 'unbound' says that everything is OK, DNSSEC is OK, testing is OK.
>> 
>> But IPFire-GUI tells me that for 'rDNS' "Reverse lookup failed".
>> 
>> Can anyone confirm? Reason?
> 
> Yes we don't have Reverse Pointers set up:
> 
>   https://bugzilla.ipfire.org/show_bug.cgi?id=11686

Ok, I see.

> Reason? Time :)

Time is definitely NOT on our side... :-)

Best,
Matthias

  reply	other threads:[~2018-07-14 16:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-14 10:29 Matthias Fischer
2018-07-14 13:34 ` Michael Tremer
2018-07-14 16:27   ` Matthias Fischer [this message]
2018-07-16 15:02     ` Peter Müller
2018-07-16 16:48       ` Michael Tremer
2018-07-19 17:35         ` DNS.WATCH up again (was: Re: 81.3.27.54 => rDNS => Reverse lookup failed) Peter Müller
2018-07-20 15:35           ` Michael Tremer
2018-07-20 18:09             ` DNS.WATCH up again Matthias Fischer
2018-07-21 11:17               ` Michael Tremer
2018-08-04 17:41                 ` Peter Müller
2018-08-05 10:34                   ` Michael Tremer

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=08bf349d-8d7c-4871-fccf-eb4cd50e5c06@ipfire.org \
    --to=matthias.fischer@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