Hello,
From my experience you don't need to delete whole set, I was actually
doing this quite recently and discovered and interesting behavior of
BIND server - last record you add will override the TTL value for a set.
So if you add another NS record to a zone, all existing NS records will
h
> On 23 Apr 2020, at 17:31, Petr Bena wrote:
>
> Hello,
>
> From my experience you don't need to delete whole set, I was actually doing
> this quite recently and discovered and interesting behavior of BIND server -
> last record you add will override the TTL value for a set.
>
> So if you a
Hi Tony, hi List,
on Mittwoch, 22. April 2020 12:27:27 CEST Tony Finch wrote:
> Older versions of BIND can fall back to non-DNSSEC queries for DNSSEC
> zones. This can be more common if there is network disruption (I don't
> know if the CenturyLink fibre cut issues have been resolved yet...)
One o
Mark Andrews wrote:
> > On 23 Apr 2020, at 07:20, Evan Hunt wrote:
> >
> > As far as I can recall, the only way to change a TTL in nsupdate is to
> > delete the whole RRset and then add it back in the same transaction:
There's actually a standard shortcut for TTL changes which is a
consequence o
Steve Egbert wrote:
> I haven't worked on the zone syntax file yet. It hasn't changed since v9.5
> days. That should be my next subproject.
That will be great! when I use nsvi, vim gets bright red and angry about
lots of fun records like DS, SSHFP, URI, EUI48, and RFC 3597 custom
records. Which
Lars Kollstedt wrote:
> One of the arpa-Nameservers 192.5.5.241, 2001:500:2::c which is the C-Root-
> Server is shown to be not responsive for queries over UDP by DNSviz for a long
> time.
This is due to a stupid peering disagreement between a couple of very
stubborn tier 1 transit providers.
T
On 4/23/20 3:39 AM, bind-users-requ...@lists.isc.org wrote:
Where would you like bug reports sent to? GitHub, your email, elsewhere?
Site: https://github.com/egberts/vim-syntax-bind-named
Issue: https://github.com/egberts/vim-syntax-bind-named/issues
```bash
git clone https://github.com/egbe
What should happen when for a given domain:
- The domain resolves via TCP but not UDP - UDP for this domain had no response
at all.
- That authoritative nameserver hosts other domains, and those domains resolve
via UDP.
I found
https://www.isc.org/blogs/refinements-to-edns-fallback-behavior-c
On 2020-04-23 14:16, Sarah Newman wrote:
What should happen when for a given domain:
- The domain resolves via TCP but not UDP - UDP for this domain had no
response at all.
- That authoritative nameserver hosts other domains, and those domains
resolve via UDP.
Do you have an example for this?
On 4/23/20 12:41 PM, Chuck Aurora wrote:
On 2020-04-23 14:16, Sarah Newman wrote:
What should happen when for a given domain:
- The domain resolves via TCP but not UDP - UDP for this domain had no
response at all.
- That authoritative nameserver hosts other domains, and those domains
resolve vi
Sarah Newman wrote:
> What should happen when for a given domain:
>
> - The domain resolves via TCP but not UDP - UDP for this domain had no
> response at all.
I would expect the domain to be completely unresolvable: the resolver will
only try TCP if it gets a truncated reaponse over UDP.
> - T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
https://www.five-ten-sg.com/mapper/bind contains links to the source
rpms, and build instructions.
geoip support is not available, since geoip2 is not available in the
epel repositories.
libuv is in the EL7 epel repository; for EL6 a link is includ
12 matches
Mail list logo
