> On 1 May 2024, at 22:25, Walter H. via bind-users
> wrote:
>
> On 01.05.2024 01:33, Mark Andrews wrote:
>>
>>> On 1 May 2024, at 03:32, Lee wrote:
>>>
>>> On Mon, Apr 29, 2024 at 11:40 PM Walter H. wrote:
On 29.04.2024 22:19, Lee wrote:
> On Sun, Apr 28, 2024 at 2:18 AM Walter
On 01.05.2024 01:33, Mark Andrews wrote:
On 1 May 2024, at 03:32, Lee wrote:
On Mon, Apr 29, 2024 at 11:40 PM Walter H. wrote:
On 29.04.2024 22:19, Lee wrote:
On Sun, Apr 28, 2024 at 2:18 AM Walter H. via bind-users
wrote:
something that I replied to and got this in response:
Error Icon
> On 1 May 2024, at 03:32, Lee wrote:
>
> On Mon, Apr 29, 2024 at 11:40 PM Walter H. wrote:
>>
>> On 29.04.2024 22:19, Lee wrote:
>>> On Sun, Apr 28, 2024 at 2:18 AM Walter H. via bind-users
>>> wrote:
>>>
>>> something that I replied to and got this in response:
>>>
>>> Error Icon
>>>
On Tue, Apr 30, 2024 at 2:40 AM Mark Andrews wrote:
>
> And it has been fixed.
Yay! No more error messages in the log because of them :-)
Thanks for your help
Lee
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this
On Mon, Apr 29, 2024 at 11:40 PM Walter H. wrote:
>
> On 29.04.2024 22:19, Lee wrote:
> > On Sun, Apr 28, 2024 at 2:18 AM Walter H. via bind-users
> > wrote:
> >
> > something that I replied to and got this in response:
> >
> > Error Icon
> > Message blocked
> > Your message to
And it has been fixed.
% dig dnssec-analyzer.verisignlabs.com
;; BADCOOKIE, retrying.
; <<>> DiG 9.19.24-dev <<>> dnssec-analyzer.verisignlabs.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9048
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1,
> On 30 Apr 2024, at 13:39, Walter H. via bind-users
> wrote:
>
> On 29.04.2024 22:19, Lee wrote:
>> On Sun, Apr 28, 2024 at 2:18 AM Walter H. via bind-users
>> wrote:
>>
>> something that I replied to and got this in response:
>>
>> Error Icon
>> Message blocked
>> Your message to
On 29.04.2024 22:19, Lee wrote:
On Sun, Apr 28, 2024 at 2:18 AM Walter H. via bind-users
wrote:
something that I replied to and got this in response:
Error Icon
Message blocked
Your message to Walter.H@[..snip..] has been blocked. See technical
details below for more information.
The
On Mon, Apr 29, 2024 at 5:13 PM Mark Andrews wrote:
>
> I prefer to only name and shame when I’m 100% sure of the target.
I was only trying to understand why I was getting a SERVFAIL, there
was no intention to name & shame.
Regards,
Lee
"name & shame" was not my intent.
>
> --
> Mark Andrews
>
I prefer to only name and shame when I’m 100% sure of the target.
--
Mark Andrews
> On 30 Apr 2024, at 06:56, Lee wrote:
>
> On Sun, Apr 28, 2024 at 7:56 PM Mark Andrews wrote:
>>
>> It isn’t DNSSEC. It’s a badly configured DNS server that is claiming that it
>> serves .com rather than
On Sun, Apr 28, 2024 at 7:56 PM Mark Andrews wrote:
>
> It isn’t DNSSEC. It’s a badly configured DNS server that is claiming that it
> serves .com rather than dnssec-analyzer-gslb.verisignlabs.com which is
> actually delegated to it.
>
> % dig dnssec-analyzer-gslb.verisignlabs.com +trace
And the SMTP server doesn’t need to listen on IPv6 if it isn’t going to accept
messages over that transport. Talk about a way to DoS yourself.
--
Mark Andrews
> On 30 Apr 2024, at 06:19, Lee wrote:
>
> On Sun, Apr 28, 2024 at 2:18 AM Walter H. via bind-users
> wrote:
>
> something that I
On Sun, Apr 28, 2024 at 2:18 AM Walter H. via bind-users
wrote:
something that I replied to and got this in response:
Error Icon
Message blocked
Your message to Walter.H@[..snip..] has been blocked. See technical
details below for more information.
The response from the remote server was:
554
On Sun, Apr 28, 2024 at 2:18 AM Walter H. wrote:
>
> On 27.04.2024 16:54, Lee wrote:
> > On Sat, Apr 27, 2024 at 9:50 AM Walter H. via bind-users
> > wrote:
> >> # host dnssec-analyzer.verisignlabs.com
> >> dnssec-analyzer.verisignlabs.com is an alias for
> >>
It isn’t DNSSEC. It’s a badly configured DNS server that is claiming that it
serves .com rather than dnssec-analyzer-gslb.verisignlabs.com which is actually
delegated to it.
% dig dnssec-analyzer-gslb.verisignlabs.com +trace +all
;; BADCOOKIE, retrying.
; <<>> DiG 9.19.24-dev <<>>
|Try these four
|
|
|
|fail01.dnssec.works|
|fail02.dnssec.works|
|fail03.dnssec.works|
|fail04.dnssec.works|
and then with +cd and note the difference;
On 28.04.2024 08:17, Walter H. via bind-users wrote:
On 27.04.2024 16:54, Lee wrote:
On Sat, Apr 27, 2024 at 9:50 AM Walter H. via
On 27.04.2024 16:54, Lee wrote:
On Sat, Apr 27, 2024 at 9:50 AM Walter H. via bind-users
wrote:
# host dnssec-analyzer.verisignlabs.com
dnssec-analyzer.verisignlabs.com is an alias for
dnssec-analyzer-gslb.verisignlabs.com.
dnssec-analyzer-gslb.verisignlabs.com has address 209.131.158.42
On Sat, Apr 27, 2024 at 9:50 AM Walter H. via bind-users
wrote:
>
> # host dnssec-analyzer.verisignlabs.com
> dnssec-analyzer.verisignlabs.com is an alias for
> dnssec-analyzer-gslb.verisignlabs.com.
> dnssec-analyzer-gslb.verisignlabs.com has address 209.131.158.42
>
Right, the IPv4 address
# host dnssec-analyzer.verisignlabs.com
dnssec-analyzer.verisignlabs.com is an alias for
dnssec-analyzer-gslb.verisignlabs.com.
dnssec-analyzer-gslb.verisignlabs.com has address 209.131.158.42
On 27.04.2024 01:35, Lee wrote:
dig dnssec-analyzer.verisignlabs.com
gives me a SERVFAIL &
19 matches
Mail list logo
