On Thu, Mar 10, 2011 at 01:24:01PM -0800,
Matt Rae wrote
a message of 54 lines which said:
> sounds like a solution would be to transfer the zone files outside
> of bind.
The solution to what? There is no problem at all, the files are
absolutely identical after the transfer. The only issue is
On 11/03/11 15:53, John Wobus wrote:
On Mar 10, 2011, at 4:24 PM, Matt Rae wrote:
Thanks guys, sounds like a solution would be to transfer the zone
files outside of bind. I'll give some of the suggestions a try.
Matt
I can't help but be curious. What problem would be solved by
transferring th
On Mar 10, 2011, at 4:24 PM, Matt Rae wrote:
Thanks guys, sounds like a solution would be to transfer the zone
files outside of bind. I'll give some of the suggestions a try.
Matt
I can't help but be curious. What problem would be solved by
transferring the zone files outside of bind?
John
Thanks guys, sounds like a solution would be to transfer the zone
files outside of bind. I'll give some of the suggestions a try.
Matt
On Wed, Mar 9, 2011 at 1:01 PM, John Wobus wrote:
> On Mar 9, 2011, at 1:09 PM, Matt Rae wrote:
>>
>> Hi, I'm working on setting up a slave dns server. Dots have
On Mar 9, 2011, at 1:09 PM, Matt Rae wrote:
Hi, I'm working on setting up a slave dns server. Dots have
historically been used in the hostnames here. The dots cause the
resulting zone file from a zone transfer to have $ORIGIN automatically
set assuming the dots are indicating a subdomain.
Here's
On 03/09/2011 06:09 PM, Matt Rae wrote:
Hi, I'm working on setting up a slave dns server. Dots have
historically been used in the hostnames here. The dots cause the
resulting zone file from a zone transfer to have $ORIGIN automatically
set assuming the dots are indicating a subdomain.
Oh god, n
On Mar 9, 2011, at 1:09 PM, Matt Rae wrote:
Hi, I'm working on setting up a slave dns server. Dots have
historically been used in the hostnames here. The dots cause the
resulting zone file from a zone transfer to have $ORIGIN automatically
set assuming the dots are indicating a subdomain.
Here
On 3/9/2011 1:09 PM, Matt Rae wrote:
Hi, I'm working on setting up a slave dns server. Dots have
historically been used in the hostnames here.
What does the term "hostname" mean to you?
If "hostname" is defined as "the contents of the first label of a
dot-delimited DNS name", then "dot in host
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There are a lot of unfortunate practices one can find in DNS names. I'd
personally recommend not doing anything that conflicts with the RFC. At
my place of business, we slave a zone from a group that has underscores
in the hostnames which is also not a
RFC 952 was the original
follow-ons are RFC 1123 and 1178
Unless you write a script to parse your file and queries I know of no way around this.
We use hypens instead of dots in our names.Mar 9, 2011 01:10:50 PM, matt...@gmail.com wrote:
Hi, I'm working on setting up a slave dns server. Dots ha
The dots delineate domains even if you don't view it as a new domain.
-Ben Croswell
On Mar 9, 2011 1:13 PM, "Matt Rae" wrote:
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Hi, I'm working on setting up a slave dns server. Dots have
historically been used in the hostnames here. The dots cause the
resulting zone file from a zone transfer to have $ORIGIN automatically
set assuming the dots are indicating a subdomain.
Here's an example of what's happening:
master zone
12 matches
Mail list logo
