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
On Wed, Mar 9, 2011 at 1:01 PM, John Wobus <jw...@cornell.edu> 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
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 file:
$ORIGIN example.com.
host1.set1 A x.x.x.x
host2.set1 A x.x.x.x
host3.set1 A x.x.x.x
slave's zone file after axfr:
$ORIGIN set1.example.com.
host1 A x.x.x.x
host2 A x.x.x.x
host3 A x.x.x.x
Is there a way to have it not change the ORIGIN and assume the dots
are a subdomain?
I bet you can't change that, but it doesn't
matter to Bind or the DNS. The two files
mean the same thing. ORIGIN doesn't
"assume" anything about subdomains: it's
just a convenience for abbreviating the
file.
If you need a consistent format for
some purpose, you could use the output
of named-compilezone.
John
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
