OS X/iOS autocorrect doesn't work well for technology conversations, period.
It's always changing words and acronyms to other things more "interesting." I
swear it waits till the moment you hit send.
--
*Note: UMDNJ is now Rutgers-Biomedical and Health Sciences*
|| \\UTGERS |--
On 28 Sep 2014, at 08:37 , LuKreme wrote:
> This is all very interesting. To be honest, I first figured out how to
> generate named.con and the domain failed
Sigh.
named.conf and the domain files. I swear, my typos and OS X autocorrect do
*not* get along.
--
K is for KATE who was struck by
> On 27 Sep 2014, at 15:46 , Doug Barton wrote:
>
> On 9/25/14 4:49 PM, LuKreme wrote:
>
>> Wait a second, so the zone name comes from the named.conf?
>
> Not quite. When named loads the zone file it does it in the context of
> the zone stanza from named.conf. If the zone name in the SOA is li
In article ,
Doug Barton wrote:
> The subsequent uses of the @ sign will inherit their labels from the
> context of the previous label.
The @ always gets replaced with the current origin. The origin starts
out as the zone name from named.conf, and only changes when you use the
$ORIGIN direct
On 9/25/14 4:49 PM, LuKreme wrote:
Wait a second, so the zone name comes from the named.conf?
Not quite. When named loads the zone file it does it in the context of
the zone stanza from named.conf. If the zone name in the SOA is listed
literally then named will check to make sure that it match
> > Note that there are only relative names in my example. This could
> > load as any zone name. You might want to use some fully-qualified
> > names on the RHS, such as "root.covisp.net." as the SOA RNAME.
>
> Wait a second, so the zone name comes from the named.conf?
Yes.
> I could have, f
On 10 Sep 2014, at 04:55 , /dev/rob0 wrote:
> "@" refers to the current $ORIGIN. When a zone file is initially
> loaded, $ORIGIN is implicitly set to the name of the zone. But you
> changed that, it's now the root! So "@" here means ".", and no, a
> zone file with "@" is not the same as a zo
I know you said, "Never mind," but you seem to be misunderstanding
something here ...
On Tue, Sep 09, 2014 at 07:42:56PM -0600, LuKreme wrote:
> # named-checkconf -z | grep -v loaded
> master/bt.tld:3: ignoring out-of-zone data (bt.tld)
> master/bt.tld:15: ignoring out-of-zone data (webdav.bt.tld
In message , LuKreme writes:
> On 09 Sep 2014, at 19:42 , LuKreme wrote:
> > # named-checkconf -z | grep -v loaded
>
> Never mind. I recreated the files from scratch and the errors went away.
Which, presumably, is because all the records have relative names. You
still need to fix named.conf be
On 09 Sep 2014, at 19:42 , LuKreme wrote:
> # named-checkconf -z | grep -v loaded
Never mind. I recreated the files from scratch and the errors went away.
--
I DID NOT SEE ELVIS Bart chalkboard Ep. 7G07
___
Please visit https://lists.isc.org/mailma
In message <3cadc2fc-7338-4ac0-a6a2-c1aac48cb...@kreme.com>, LuKreme writes:
> # named-checkconf -z | grep -v loaded
> master/bt.tld:3: ignoring out-of-zone data (bt.tld)
> master/bt.tld:15: ignoring out-of-zone data (webdav.bt.tld)
> _default/dw.tld/IN: bad zone
> master/bt.tld:16: ignoring out-o
# named-checkconf -z | grep -v loaded
master/bt.tld:3: ignoring out-of-zone data (bt.tld)
master/bt.tld:15: ignoring out-of-zone data (webdav.bt.tld)
_default/dw.tld/IN: bad zone
master/bt.tld:16: ignoring out-of-zone data (www.bt.tld)
zone dw.tld/IN: has 0 SOA records
zone dw.tld/IN: has no NS rec
12 matches
Mail list logo
