<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 9/03/2013 11:28 p.m., Noel Butler
wrote:<br>
</div>
<blockquote cite="mid:1362824923.11475.20.camel@tardis" type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="GENERATOR" content="GtkHTML/3.28.3">
<br>
<blockquote type="CITE"> I've got active ns on v4, though not on
that offending server, it's actually pushing ns changes to an
upstream.<br>
<br>
I have discovered that I have no idea how PTR records work at
all.<br>
<br>
</blockquote>
<br>
Much the same as normal zones work<br>
<br>
<blockquote type="CITE"> I've done a stack of reading and still
don't understand how to set bind up.<br>
<br>
</blockquote>
<br>
Well, my posts give you two working examples <img
src="cid:part1.04070002.07070205@bowenvale.co.nz" alt=":)"
align="middle" border="0"> just remember in PTR zones the
hostnames must end with a period.<br>
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 PTR foo.bar.com.
<br>
<br>
remember to pad out the zeros, no shortcuts, ::44 is<br>
<br>
4.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0<br>
<br>
where as in forward zones they do not and you enter them in as
normal, and you abbreviate the hostname , eg:<br>
<br>
foo A 2a00:1c18::44<br>
<br>
<br>
</blockquote>
<br>
Ya, I already knew all that. (Just saying so you get a better
picture of where my understanding is at, not trying to be ungrateful
:) )<br>
<br>
<blockquote cite="mid:1362824923.11475.20.camel@tardis" type="cite">
But you should play first in a kind of sandpit, because as you
know DNS is very important, if you screw it up, you can might as
well pull the ethernet cables out because you'll become just as
invisible.<br>
<br>
</blockquote>
ya. considered that. Been thinking how and where I set up a
sandpit.<br>
<br>
<blockquote cite="mid:1362824923.11475.20.camel@tardis" type="cite">
<blockquote type="CITE"> I'm not even sure what questions to ask
at present. <br>
</blockquote>
<br>
Then you need to consider:<br>
<br>
1/ is this going to be a cache server as well proving any lookups,
or only serving the delegated zone(s)<br>
- If true, then your config is minimal.<br>
<br>
2/ do you intend to serve the domain hostname as well or just the
reverse zone for your ipv6 allocation.<br>
- If true, then it's just as simple.<br>
<br>
The Bind manual "ARM9" is very handy with examples, as you'll see
if you compare my previous two examples with the manual.<br>
<br>
If you have any specific questions ARM or google cant answer, just
ask, though I usually only check this a/c once a day - nbles sits
miserable weather and I'm bored heh.<br>
<br>
Cya<br>
<br>
</blockquote>
<br>
Someone posted a link to a config generator.<br>
<br>
I don't know what to do with the output it makes.<br>
<br>
Clearly I just copy and paste it into a file and out it on the
machine, but where?<br>
<br>
Clearly that file needs to be linked into the existing config files
in some way, but where?<br>
<br>
I need to link it in such way that it doesn't break DTC (the control
panel), but where and how?<br>
<br>
I need to link it in such a way that DTC doesn't break it next time
DTC does an update of anything, but where and how?<br>
<br>
I don't know what DTC actually does or how it does it. I think it
just manually writes bind files, adds them to the bind conf file and
then restarts bind to pick up the changes.<br>
<br>
I then need to do this in such a way that the underlying config
files are consistant with what DTC does now so that I can then
recode DTC to do this stuff for me (and everyone else who uses DTC),
but I don't know how I should approach that?<br>
<br>
I haven't set up anything to do with PTR before other than setting
the PTR records for the IPs on my own VPS server which is done by
just using a feature in the DTC control panel.<br>
<br>
In the case of my .nz connections, I don't have delegation of the IP
space. I just ask DTC to set PTR records for me at $20 a time.
They don't have a control panel to delegate my /29<br>
<br>
Ok. so now you understand a bit more about where I'm at. I think
the approach is to do what Mark says... just chip, chip, chip.<br>
<br>
First thing is to get some sandpit in place that it doesn't matter
if I break it and not dabble on my production systems.<br>
<br>
D<br>
<br>
<pre class="moz-signature" cols="72">--
Don Gould
31 Acheson Ave
Mairehau
Christchurch, New Zealand
Ph: + 64 3 348 7235
Mobile: + 64 21 114 0699
</pre>
</body>
</html>