I'm doing an nsupdate to a remote server from my desktop
cat nsupdate.txt
server ns01.example.com
debug yes
zone example.net.
update add test.example.net. 500 in TXT "TEST STRING"
show
send
nsupdate -k ./jason-key ./nsupdate.tx
On 24/04/16 21:04, jaso...@mail-central.com wrote:
Hey Jason,
> checking with dig, it's NOT in 'TXT' where I expected it
>
> dig TXT example.net +short
> (empty)
You added a TXT record for the name test.example.net, but you're looking
for it at the name example.net. Of cours
On Sun, Apr 24, 2016, at 12:20 PM, Anand Buddhdev wrote:
> On 24/04/16 21:04, jaso...@mail-central.com wrote:
>
> Hey Jason,
>
> > checking with dig, it's NOT in 'TXT' where I expected it
> >
> > dig TXT example.net +short
> > (empty)
>
> You added a TXT record for the name te
In message <1461526649.3652904.588164577.6d131...@webmail.messagingengine.com>,
jaso...@mail-central.com writes:
>
>
> On Sun, Apr 24, 2016, at 12:20 PM, Anand Buddhdev wrote:
> > On 24/04/16 21:04, jaso...@mail-central.com wrote:
> >
> > Hey Jason,
> >
> > > checking with dig, it's NOT in 'T
On Sun, Apr 24, 2016 at 12:04:15PM -0700, jaso...@mail-central.com wrote:
> I'm doing an nsupdate to a remote server from my desktop
>
> cat nsupdate.txt
>server ns01.example.com
>debug yes
>zone example.net.
>update add test.example.net. 500 in TXT "TEST STRI
In message <20160424222541.gb22...@harrier.slackbuilds.org>, /dev/rob0 writes:
> On Sun, Apr 24, 2016 at 12:04:15PM -0700, jaso...@mail-central.com wrote:
> > I'm doing an nsupdate to a remote server from my desktop
> >
> > cat nsupdate.txt
> > server ns01.example.com
> > debug yes
I'm in over my head a bit on these details, so appreciate the help.
> The smoking gun is in the hand of systemctl ...
Hadn't thought of that, but not surprised to hear it.
I inherited this, and didn't yet monkey with systemd. But I can as needed.
Here's the systemd unit file for named:
> What is deleting your journal? It's not named doing that.
Hm.
Maybe this
destroy_chroot() {
cp -af ${CHROOT}/namedb/master/*.signed
/opt/etc/named/namedb/master/
should be
destroy_chroot() {
cp -af ${CHROOT}/namedb/master/*.{jnl,signed}
/opt
> This zone would not pass named-checkzone, which interestingly, is the same
> code which named itself uses when initially loading a zone.
It appears to
named-checkzone -t /var/chroot/named example.com
/namedb/master/example.com.zone
zone example.com/IN: loaded serial 14
9 matches
Mail list logo
