Re: PTR format question
In article mailman.897.1269129914.21153.bind-us...@lists.isc.org, groups gro...@obsd.us wrote: I did not know there were MACROs available.. as I just inheirited this legacy system less than one month ago.. There aren't macros, just one special tool for creating a block of DNS entries that contain sequential numbers in them. What does it being a legacy system have to do with it? It's running a recent version of BIND, that's all that matters for this. -- Barry Margolin, bar...@alum.mit.edu Arlington, MA *** PLEASE don't copy me on replies, I'll read them in the group *** ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: PTR format question
Barry Margolin wrote, On 03/21/2010 04:22 AM: In article mailman.897.1269129914.21153.bind-us...@lists.isc.org, groups gro...@obsd.us wrote: I did not know there were MACROs available.. as I just inheirited this legacy system less than one month ago.. There aren't macros, just one special tool for creating a block of DNS entries that contain sequential numbers in them. Thx for the clarification. What does it being a legacy system have to do with it? It's running a recent version of BIND, that's all that matters for this. Bind is current.. yes.. I rebuilt the box.. the OS I know and can support.. The zone format specifically the PTR has been severely neglected and to me is legacy . And you saw the format of the PTR records.. There are several of those in that format .. The suggestion of the $GENERATE has been priceless ... Thx Charles ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: PTR format question
On Mar 21, 2010, at 2:22 AM, Barry Margolin wrote: In article mailman.897.1269129914.21153.bind-us...@lists.isc.org, groups gro...@obsd.us wrote: I did not know there were MACROs available.. as I just inheirited this legacy system less than one month ago.. There aren't macros, just one special tool for creating a block of DNS entries that contain sequential numbers in them. pedant Well I think that you could make a reasonable case that $GENERATE is a macro: An abstraction whereby a certain textual pattern is replaced according to a defined set of rules and http://en.wikipedia.org/wiki/Macro_(computer_science) /pedant Sorry, just being difficult, W What does it being a legacy system have to do with it? It's running a recent version of BIND, that's all that matters for this. -- Barry Margolin, bar...@alum.mit.edu Arlington, MA *** PLEASE don't copy me on replies, I'll read them in the group *** ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users smime.p7s Description: S/MIME cryptographic signature ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
PTR format question
In the process of cleaning up a much neglected PTR file Bind: 9.6.2.1 OS: CentOS 5.4 Current PTR in this format: (1 tab between entries) $ORIGIN 58.172.in-addr.arpa. $ORIGIN 0.58.172.in-addr.arpa. 11PTRnat-172-58-0-11.example.com. 12PTRnat-172-58-0-12.example.com. ... $ORIGIN 58.172.in-addr.arpa. $ORIGIN 1.58.172.in-addr.arpa. 21PTRnat-172-58-1-21.example.com. 22PTRnat-172-58-1-22.example.com. ... $ORIGIN 58.172.in-addr.arpa. $ORIGIN 2.58.172.in-addr.arpa. 31 PTR nat-172-58-2-31.example.com. 32 PTR nat-172-58-2-32.example.com. ... I have to redo the entire subnets.. it will be a very large file.. My question is this the most efficient way to do this..? Thx Charles ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: PTR format question
groups wrote: In the process of cleaning up a much neglected PTR file Bind: 9.6.2.1 OS: CentOS 5.4 Current PTR in this format: (1 tab between entries) $ORIGIN 58.172.in-addr.arpa. $ORIGIN 0.58.172.in-addr.arpa. 11PTRnat-172-58-0-11.example.com. 12PTRnat-172-58-0-12.example.com. ... $ORIGIN 58.172.in-addr.arpa. $ORIGIN 1.58.172.in-addr.arpa. 21PTRnat-172-58-1-21.example.com. 22PTRnat-172-58-1-22.example.com. ... $ORIGIN 58.172.in-addr.arpa. $ORIGIN 2.58.172.in-addr.arpa. 31 PTR nat-172-58-2-31.example.com. 32 PTR nat-172-58-2-32.example.com. ... $ORIGIN 0.58.172.in-addr.arpa. $GENERATE 11-... $ PTR nat-172-58-0-$.example.com. $ORIGIN 1.58.172.in-addr.arpa. $GENERATE 21-... $ PTR nat-172-58-1-$.example.com. Do note that these ranges look suspicious. AlanC signature.asc Description: OpenPGP digital signature ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: PTR format question
First off, please don't grab an unrelated message and reply to it when starting a new thread. Please actually post a new message. In the process of cleaning up a much neglected PTR file Bind: 9.6.2.1 OS: CentOS 5.4 Current PTR in this format: (1 tab between entries) $ORIGIN 58.172.in-addr.arpa. $ORIGIN 0.58.172.in-addr.arpa. Including $ORIGIN in the body of the zone file is usually a bad idea, and almost always unnecessary. It's definitely a bad idea to do it twice in a row with different $ORIGINs, and a worse idea to include that same thing multiple times. 11PTRnat-172-58-0-11.example.com. 12PTRnat-172-58-0-12.example.com. I have to redo the entire subnets.. it will be a very large file.. My question is this the most efficient way to do this..? Sorry, it's not at all clear what you have to change. Are you saying that you have to change the hostnames for all the PTRs in the zone? If so, and you're doing the same kind of pattern-based hostnames you could simply use $GENERATE. Something like: $GENERATE 0-255 $ PTR dynamic-172-58-0-$.example.com. You can read more about $GENERATE in the ARM. hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: PTR format question
groups wrote: In the process of cleaning up a much neglected PTR file Bind: 9.6.2.1 OS: CentOS 5.4 Current PTR in this format: (1 tab between entries) $ORIGIN 58.172.in-addr.arpa. $ORIGIN 0.58.172.in-addr.arpa. 11PTRnat-172-58-0-11.example.com. 12PTRnat-172-58-0-12.example.com. ... $ORIGIN 58.172.in-addr.arpa. $ORIGIN 1.58.172.in-addr.arpa. 21PTRnat-172-58-1-21.example.com. 22PTRnat-172-58-1-22.example.com. ... $ORIGIN 58.172.in-addr.arpa. $ORIGIN 2.58.172.in-addr.arpa. 31 PTR nat-172-58-2-31.example.com. 32 PTR nat-172-58-2-32.example.com. ... $ORIGIN 0.58.172.in-addr.arpa. $GENERATE 11-... $ PTR nat-172-58-0-$.example.com. $ORIGIN 1.58.172.in-addr.arpa. $GENERATE 21-... $ PTR nat-172-58-1-$.example.com. Do note that these ranges look suspicious. AlanC ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users Alan.. I inherited this box.. and am really wanting to make this much more simple since this isn't my primary job.. I just changed the some of the numbers.. this is the actual format of my real PTR zone file. I am going to read up on $GENERATE function.. Reminds me of my macros on my OpenBSD firewall.. Much Thanks.. Charles ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: PTR format question
First off, please don't grab an unrelated message and reply to it when starting a new thread. Please actually post a new message. Doug.. I grabbed the wrong thread.. Actually double posted too.. :-/ In the process of cleaning up a much neglected PTR file Bind: 9.6.2.1 OS: CentOS 5.4 Current PTR in this format: (1 tab between entries) $ORIGIN 58.172.in-addr.arpa. $ORIGIN 0.58.172.in-addr.arpa. Including $ORIGIN in the body of the zone file is usually a bad idea, and almost always unnecessary. It's definitely a bad idea to do it twice in a row with different $ORIGINs, and a worse idea to include that same thing multiple times. 11PTRnat-172-58-0-11.example.com. 12PTRnat-172-58-0-12.example.com. I have to redo the entire subnets.. it will be a very large file.. My question is this the most efficient way to do this..? Sorry, it's not at all clear what you have to change. Are you saying that you have to change the hostnames for all the PTRs in the zone? If so, and you're doing the same kind of pattern-based hostnames you could simply use $GENERATE. Something like: $GENERATE 0-255 $ PTR dynamic-172-58-0-$.example.com. You can read more about $GENERATE in the ARM. hth, Doug I did not know there were MACROs available.. as I just inheirited this legacy system less than one month ago.. Trying to do my best since this isn't my only job.. :P Thx for the reply.. Charles ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
