> On 23 Apr 2020, at 07:20, Evan Hunt wrote:
>
> On Wed, Apr 22, 2020 at 03:04:38PM -0600, @lbutlr via bind-users wrote:
>> # nsupdate -k /path/to/key
>>> zone example.com
>>> ttl 3600
>>> send
>>> ^d
>>
>> No errors, but no change in the TTL.
>
> "ttl 3600" just means "from now on assume I
On 4/22/20 12:32 PM, Steve Egbert wrote:
Hello, Bind-Users,
Hi,
This is my 2nd post (in 19 years).
Welcome.
I'm announcing the release of ISC Bind v9.16 named.conf syntax file for
Vim editor.
Thank you!
The color scheme is derived from default Vim highlights using your own
color
On Wed, Apr 22, 2020 at 03:04:38PM -0600, @lbutlr via bind-users wrote:
> # nsupdate -k /path/to/key
> > zone example.com
> > ttl 3600
> > send
> > ^d
>
> No errors, but no change in the TTL.
"ttl 3600" just means "from now on assume I mean ttl 3600 in all the
records I send". You didn't
What is the proper syntax gor changing the TTL on a zone with nsupdate?
Does the existence of $TTL 86400 in the domain.conf file override nssupdate’s
attempts to change the TTL?
# nsupdate -k /path/to/key
> zone example.com
> ttl 3600
> send
> ^d
No errors, but no change in the TTL.
--
"I
I'm slowly working on a dialog with the Vim maintainer. But before I do
that "final" submission, it would make sense to vet this a bit more
solidly before I 'mainstream' this.
On 4/22/20 3:25 PM, Evan Hunt wrote:
On Wed, Apr 22, 2020 at 02:32:51PM -0400, Steve Egbert wrote:
I'm announcing
On Wed, Apr 22, 2020 at 02:32:51PM -0400, Steve Egbert wrote:
> I'm announcing the release of ISC Bind v9.16 named.conf syntax file for
> Vim editor.
Oh, thank you *so much*! That itch needed scratching for a long,
long time. :)
Are you planning to submit this upstream to vim, by any chance?
I haven't worked on the zone syntax file yet. It hasn't changed since
v9.5 days.
That should be my next subproject. (Which should go by rather quickly
given that I've a mastery on Vim syntax, I hope).
S.
On 4/22/20 2:50 PM, Hugo Salgado wrote:
Thanks a lot Steve, works like a charm!
It's
Thanks a lot Steve, works like a charm!
It's nice to have well formatted SSHFP records at last! :)
Regards,
Hugo Salgado
On 14:32 22/04, Steve Egbert wrote:
> Hello, Bind-Users,
>
>
> This is my 2nd post (in 19 years).
>
> I'm announcing the release of ISC Bind v9.16 named.conf syntax file
Hello, Bind-Users,
This is my 2nd post (in 19 years).
I'm announcing the release of ISC Bind v9.16 named.conf syntax file for
Vim editor.
Yeah, the last one is the Vim stock 'named.conf' syntax and probably
works marginally today as it was written for Bind 9.4-9.5.
No auto-installer yet.
Thank you to everyone taking the time to reply and provide guidance with this
problem.
Our cisco guy turned off alg on the nat for dns and our reverse dns lookups are
now working properly.
Just to follow up, found this after searching using Ondřej Surý's description
and Reindl Harald's
Carl,
The output from the tcpdumps on both machines.
>From my local:
226 13.386290 172.16.1.10372.162.32.4 DNS 107
Standard query 0x8148 PTR 3.32.162.72.in-addr.arpa OPT
227 13.405397 72.162.32.4 172.16.1.103DNS 93
Standard query response
Lars Kollstedt wrote:
>
> what do the following messages in loose combination mean?:
>
> Apr 22 09:23:01 resolver1 named[1201]: validating ip6.arpa/SOA: got insecure
> response; parent indicates it should be secure
This means there is a DS record for ip6.arpa in the .arpa zone, but there
were
Hi,
what do the following messages in loose combination mean?:
Apr 22 09:23:01 resolver1 named[1201]: validating ip6.arpa/SOA: got insecure
response; parent indicates it should be secure
[...]
Apr 22 09:32:23 resolver1 named[1201]: validating in-addr.arpa/SOA: got
insecure response; parent
13 matches
Mail list logo
