The way I've solved this in the past is to create a zone file template with
"variables" in the text that are easy to find. EG:
[TIMESTAMP]
is where the number goes. All my zone files are managed by a script that
parses the template files with values appropriate for each domain.
On Wed, Oct 17, 2
Allegedly, on or about 17 October 2018, Mike Wright sent:
> I have a set of dns zone text files in "bind" format. On the fourth
> line there is a 10 digit timestamp (ignoring white space, the first
> field). There is no way to predetermine the value so search and
> replace by value is a no go a
On 10/17/2018 12:19 PM, Chris Adams wrote:
The BIND zone file format is very unfriendly for easy script changes
unfortunately.
Please note that he already knows that he only needs to examine the
fourth line in every file.
___
users mailing list -- u
On 10/17/18 11:04 AM, Mike Wright wrote:
I have a set of dns zone text files in "bind" format. On the fourth
line there is a 10 digit timestamp (ignoring white space, the first
field). There is no way to predetermine the value so search and replace
by value is a no go and seems to require som
On 10/17/2018 12:04 PM, Mike Wright wrote:
Hi all,
I have a set of dns zone text files in "bind" format. On the fourth
line there is a 10 digit timestamp (ignoring white space, the first
field). There is no way to predetermine the value so search and replace
by value is a no go and seems to
Once upon a time, Mike Wright said:
> I have a set of dns zone text files in "bind" format. On the fourth
> line there is a 10 digit timestamp (ignoring white space, the first
> field). There is no way to predetermine the value so search and
> replace by value is a no go and seems to require som
Hi all,
I have a set of dns zone text files in "bind" format. On the fourth
line there is a 10 digit timestamp (ignoring white space, the first
field). There is no way to predetermine the value so search and replace
by value is a no go and seems to require some positional approach such
as "
