Hello I think you should use DNAME, like CNAME but for domain.
Regards, Baptiste Dupont De : Pdns-users [mailto:pdns-users-boun...@mailman.powerdns.com] De la part de Mohamad F. Barham Envoyé : mardi 24 juillet 2018 09:28 À : Brian Candler; pdns-users@mailman.powerdns.com Objet : Re: [Pdns-users] Supporting ALIAS Records with DNSSEC specially with powerDNS-Admin as managment tool Thanks Brian for your fast response,,, you got exactly what I need (mirror entire domain to another), is there a way to do that? _____ From: Brian Candler <b.cand...@pobox.com> Sent: Tuesday, July 24, 2018 10:05:41 AM To: Mohamad F. Barham; pdns-users@mailman.powerdns.com Subject: Re: [Pdns-users] Supporting ALIAS Records with DNSSEC specially with powerDNS-Admin as managment tool On 24/07/2018 07:21, Mohamad F. Barham wrote: > and I Editted powerDNS-Admin to Support ALIAS, > Now What I want is to make these domains ALIASES > (bzu.ps,birzeit.edu.ps, birzeit.ps) for this domain (birzeit.edu) > where shoud I insert the ALIAS records? In which format? I think you've misunderstood what ALIAS does. ALIAS does not mirror an entire domain. ALIAS is pseudo resource-record, which expands to the dynamic lookup of another resource record. It's typically used at the apex of a zone, where you might like to insert a CNAME but you're not allowed to: CNAME cannot exist alongside any other resource type, including NS and SOA. ; not allowed @ NS ns1.mydomain.com. @ NS ns2.mydomain.com. @ CNAME web1.cloudhost.com. ; solution @ NS ns1.mydomain.com. @ NS ns2.mydomain.com. @ ALIAS web1.cloudhost.com. When someone looks up an A record for mydomain.com, they will get the A record(s) for web1.cloudhost.com, which are dynamically looked up (via the configured resolver) but returned as if they were stored in the authoritative server. See: https://doc.powerdns.com/authoritative/guides/alias.html HTH, Brian. ~~~~~~~~~~~~~~~~~~~~~~~~~~ The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The University is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. ~~~~~~~~~~~~~~~~~~~~~~~~~~ _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
