On Tue, 2020-09-29 at 12:12 +0100, Robert Mortimer via Pdns-users
wrote:
> In theory apex DNAME records should work - I've not had that much luck in
> getting them to do so.
No, DNAME records generate CNAMEs for every name -under- them. They
never do anything for their own name.
Kind regards,
--
Hi,
both excellent reasons :)
In theory you only need to retain the SOA and NS records so something like:
example.com. IN SOA ns.example.net. hostmaster.example.net. (
2015071700 ; serial
10800 ; refresh (3 hours)
For two excellent reasons:
1. I didn't know they existed.
2. Now that I know they exist - I don't know how to use them.
I've enabled DNAME processing - now I need to understand how to setup
the zone. Do replace the *entire* zone with just a DNAME record? Or do I
need to retain any of the SOA,
Obvious question any reason why you're not using DNAMEs?
https://tools.ietf.org/html/rfc2672
--
Robm
873
"Ask not what I can do for the stupid,
but what the stupid can do for me" - Graeme Garden
On 27/09/2020 21:08:37, Daniel Miller via Pdns-users
wrote:
I have a number of domains
Hi Daniel,
Are these true aliases? (As in: every record can be copied exactly as it is,
without changing anything). In that case, the ALIAS type should work for you
(https://doc.powerdns.com/authoritative/guides/alias.html).
If these are more like "templates", (eg: mydomain.com MX mail.mydomain
I have a number of domains that are simply duplicates of a base domain,
e.g. mydomain.com is the primary domain, and we also have mydomain.net
and mydomain.info.
I'd like to able to configure any/all records only in mydomain.com - and
have them "magically" propagated to the designated duplicat
