Putting weird characters into zone files ?
For a special project, I need to be able to create resource records within a BIND zone file where some of the domain labels in some of the FQDNs on the left-hand-side will need to be either (a) literal asterisks or else (b) literal exclamation marks. What's the most proper way to do this? Can I (should I) just use backslash escapes... like this? \*.foo.bar IN A127.0.0.99 \!.foo.bar IN A127.0.0.9 ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Putting weird characters into zone files ?
Hi Ronald
On Sat, Sep 27, 2014 at 04:31:07AM -0700, Ronald F. Guilmette wrote:
For a special project, I need to be able to create resource
records within a BIND zone file where some of the domain
labels in some of the FQDNs on the left-hand-side will need
to be either (a) literal asterisks or else (b) literal
exclamation marks.
What's the most proper way to do this? Can I (should I) just
use backslash escapes... like this?
\*.foo.barIN A127.0.0.99
\!.foo.barIN A127.0.0.9
For the syntax of names in a master file, see RFC 1035 section 5.
Wildcard label ('*'), whether escaped or not, has the same
representation and meaning.
BIND will not allow you to use special characters such as '!' in owner
names of certain RRs types such as A, MX, etc. as they don't form valid
hostnames (see RFCs 1123 and 1912).
Mukund
pgp3wdTvrY6zw.pgp
Description: PGP signature
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Putting weird characters into zone files ?
In message 20140927122322.ga4...@totoro.home.mukund.org,
Mukund Sivaraman m...@isc.org wrote:
On Sat, Sep 27, 2014 at 04:31:07AM -0700, Ronald F. Guilmette wrote:
For a special project, I need to be able to create resource
records within a BIND zone file where some of the domain
labels in some of the FQDNs on the left-hand-side will need
to be either (a) literal asterisks or else (b) literal
exclamation marks.
=20
What's the most proper way to do this? Can I (should I) just
use backslash escapes... like this?
=20
\*.foo.bar IN A127.0.0.99
\!.foo.bar IN A127.0.0.9
For the syntax of names in a master file, see RFC 1035 section 5.
Wildcard label ('*'), whether escaped or not, has the same
representation and meaning.
BIND will not allow you to use special characters such as '!' in owner
names of certain RRs types such as A, MX, etc. as they don't form valid
hostnames (see RFCs 1123 and 1912).
OK. Thanks for the reply. I figured out a simple work-around where
I won't need the special characters after all.
Regards,
rfg
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Two domains reporting errors
On 9/25/14 4:49 PM, LuKreme wrote: Wait a second, so the zone name comes from the named.conf? Not quite. When named loads the zone file it does it in the context of the zone stanza from named.conf. If the zone name in the SOA is listed literally then named will check to make sure that it matches, and generate an error if it does not. However, if you use the @ sign in that spot in the SOA record then named will fill in the zone name for you. The subsequent uses of the @ sign will inherit their labels from the context of the previous label. I could have, for all my hosted domains, a single file named something like hosted.conf and then simply link to it with `ln hosted.conf dw.tld` or ln -s, perhaps? Don't do that ... Just use the same file name in the zone stanzas in named.conf. Also, the SOA line contains ns? The MNAME field theoretically lists the master name server for the zone. In practice however it isn't used for anything except occasionally for dynamic DNS. hope this helps, Doug ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Putting weird characters into zone files ?
In message 65455.1411817...@server1.tristatelogic.com, Ronald F. Guilmette writes: For a special project, I need to be able to create resource records within a BIND zone file where some of the domain labels in some of the FQDNs on the left-hand-side will need to be either (a) literal asterisks or else (b) literal exclamation marks. What's the most proper way to do this? Can I (should I) just use backslash escapes... like this? \*.foo.barIN A127.0.0.99 \!.foo.barIN A127.0.0.9 Well there is no way to escape a wildcard in the DNS. As for the exclamation point just enter it. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Putting weird characters into zone files ?
Mukund Sivaraman m...@isc.org wrote: BIND will not allow you to use special characters such as '!' in owner names of certain RRs types such as A, MX, etc. as they don't form valid hostnames (see RFCs 1123 and 1912). But you can set the check-names option to relax the restrictions. Tony. -- f.anthony.n.finch d...@dotat.at http://dotat.at/ Trafalgar: Cyclonic in northwest, otherwise mainly northerly or northwesterly 5 or 6. Slight or moderate. Showers in northwest. Good. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Two domains reporting errors
In article mailman.998.1411854427.26362.bind-us...@lists.isc.org, Doug Barton do...@dougbarton.us wrote: The subsequent uses of the @ sign will inherit their labels from the context of the previous label. The @ always gets replaced with the current origin. The origin starts out as the zone name from named.conf, and only changes when you use the $ORIGIN directive. Lines inherit their label from the previous line if they start with whitespace (i.e. they have no label of their own). -- Barry Margolin Arlington, MA ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
