<html><HEAD><LINK rel=stylesheet type=text/css href="/netmail/static/deg/css/wysiwyg-3933289048.css" media=all>
<META name=GENERATOR content="MSHTML 8.00.7600.16722"></HEAD>
<BODY>
<DIV>RFC 952 was the original</DIV>
<DIV>follow-ons are RFC 1123 and 1178</DIV>
<DIV> </DIV>
<DIV>Unless you write a script to parse your file and queries I know of no way around this.</DIV>
<DIV>We use hypens instead of dots in our names.<BR><BR><BR>Mar 9, 2011 01:10:50 PM, mattrae@gmail.com wrote:<BR></DIV>
<BLOCKQUOTE style="BORDER-LEFT: rgb(102,153,204) 3px solid">Hi, I'm working on setting up a slave dns server. Dots have<BR>historically been used in the hostnames here. The dots cause the<BR>resulting zone file from a zone transfer to have $ORIGIN automatically<BR>set assuming the dots are indicating a subdomain.<BR><BR>Here's an example of what's happening:<BR><BR>master zone file:<BR><BR>$ORIGIN example.com.<BR>host1.set1 A x.x.x.x<BR>host2.set1 A x.x.x.x<BR>host3.set1 A x.x.x.x<BR><BR>slave's zone file after axfr:<BR><BR>$ORIGIN set1.example.com.<BR>host1 A x.x.x.x<BR>host2 A x.x.x.x<BR>host3 A x.x.x.x<BR><BR>Is there a way to have it not change the ORIGIN and assume the dots<BR>are a subdomain?<BR><BR>Thanks!<BR><BR>Matt Rae<BR>_______________________________________________<BR>bind-users mailing list<BR>bind-users@lists.isc.org<BR>https://lists.isc.org/mailman/listinfo/bind-users<BR></BLOCKQUOTE></BODY></html>