>
> "Novosielski, Ryan" wrote on about Friday, April 5,
>2013 10:31 PM
>
>
>>$INCLUDE db.example.com
>>@ IN A 192.168.50.50
>It may be obvious, but one needs to be aware that any $ORIGIN
statements in the included file may cause unexpected results
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I have a small python script that parses /etc/named.conf looking for
> comments indicating zones that are registered with gkg.net, and it
> uploads the current set of keys using the gkg.net api.
http://www.five-ten-sg.com/util/gkg.upload.ds
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/06/2013 03:11 AM, Doug Barton wrote:
> On 04/05/2013 11:53 PM, Novosielski, Ryan wrote:
>
> | It is funny you should mention that... my questions about using
> views | to create a situation where one single record is different
> happens to | be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/05/2013 11:53 PM, Novosielski, Ryan wrote:
| It is funny you should mention that... my questions about using views
| to create a situation where one single record is different happens to
| be exactly for this reason. The Active Directory admi
4 matches
Mail list logo