On Apr 18 2016, Dave Warren wrote:
On 2016-04-14 03:02, 'Stephane Bortzmeyer' wrote:
On Thu, Apr 14, 2016 at 11:55:04AM +0300,
Daniel Dawalibi wrote
a message of 22 lines which said:
Do you think it is better to remove it from named.root?
Certainly not, your resolver removes it automati
On 2016-04-14 03:02, 'Stephane Bortzmeyer' wrote:
On Thu, Apr 14, 2016 at 11:55:04AM +0300,
Daniel Dawalibi wrote
a message of 22 lines which said:
Do you think it is better to remove it from named.root?
Certainly not, your resolver removes it automatically from the list of
authoritative
On Thu, Apr 14, 2016 at 11:55:04AM +0300,
Daniel Dawalibi wrote
a message of 22 lines which said:
> Do you think it is better to remove it from named.root?
Certainly not, your resolver removes it automatically from the list of
authoritative servers for the zone.
> Is there any impact on the
: Re: g.root-servers.net not reachable anymore
On Thu, Apr 14, 2016 at 08:35:00AM +0200, Daniel Stirnimann
wrote a message of 14 lines which said:
> Looks like you are not alone!
>
> https://atlas.ripe.net/dnsmon/group/g-root
Only broken over UDP. Works on TCP and still replies to t
On Thu, Apr 14, 2016 at 08:35:00AM +0200,
Daniel Stirnimann wrote
a message of 14 lines which said:
> Looks like you are not alone!
>
> https://atlas.ripe.net/dnsmon/group/g-root
Only broken over UDP. Works on TCP and still replies to traceroute.
_
On 14.04.16 08:31, Daniel Dawalibi wrote:
> Anyone experiencing a reach ability issue toward g.root-servers.net?
Looks like you are not alone!
https://atlas.ripe.net/dnsmon/group/g-root
Daniel
___
Please visit https://lists.isc.org/mailman/listinfo/bin
6 matches
Mail list logo
