Anton Aylward wrote:
Per Jessen said the following on 06/02/2013 07:41 AM:
Anton Aylward wrote:
Me, I'm paranoid. I could use 23 IN PTR mail but I chose to use 23 IN PTR mail.antonaylward.com.
Please note the period. The first only works if you have the named.conf set up correctly while the latter is more robust.
Uh, the former wouldn't work at all, you have to use the latter. Your zone file presumably has a $ORIGIN directive :
$ORGIN x.168.192.in-addr.arpa.
This is used for '23' and 'mail'. That'[s why you need to use 'mail.antonaylward.com.'.
Are you contradicting yourself by showing how my first example could work?
I didn't think so, no.
Actually it might depend on what's in the named.config file that references this reverse file. That may give the origin.
lets face it, the forward files can use the short form
mail IN A 192.168.1.23
rather than
mail.antonaylward.com IN A 192.168.1.23
Right. The default $ORIGIN is the zone name from named.config.
Why? What abbreviations are you using? - "@" - ?
For normal zones, I usually have a specific $ORIGIN. For reverse zones, always.
If I have in the config file
zone "antonaylward.com" { ... }
then the "@" refers to that. This is the origin unless you over-ride it in the zone file.
Yup.
**The origin is added to names not ending in a dot**
Yes. That is why your first example with 23 IN PTR mail won't work. For a reverse zone file, you need an $ORIGIN of 'x.168.192.in-addr.arpa.' (whether explicit or from @), therefore your PTR has to be fully qualified = "mail.antonaylward.com." -- Per Jessen, Zürich (14.6°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org