Replies: 9 comments 23 replies
-
The link you have is to their managed hosting documents, are you sure they support this as their secondary zone hosting offering? The name just maps to a type, so if you find out the type they are using to specify ANAME you can add a generic typed entry to see if it works... |
Beta Was this translation helpful? Give feedback.
-
This is the response I got from DNS Made Easy support:
So my understanding is that they don't support ALIAS for their secondary DNS offering either - which makes sense. I assume they're using the same software for primary DNS as secondary DNS. Weather its their own software or a third party software.
I am not sure I follow this. Can you clarify this a bit more? What would I need to ask them? And what is a generic typed entry? Do you mean a manually created record? If so how do we create that? Something like this?
Assuming I created that wouldn't that pose an issue because PowerDNS wouldn't know to expand an ANAME record? We're using PowerDNS for primary and DNS Made Easy for secondary so both sides need to be able to parse/understand the record types. Or one side has to translate the record type for the other (I think). Unless there's some trick I'm not understanding. |
Beta Was this translation helpful? Give feedback.
-
you can do this with https://doc.powerdns.com/authoritative/modes-of-operation.html?highlight=axfrfilter#modifying-a-slave-zone-using-a-script |
Beta Was this translation helpful? Give feedback.
-
I'm trying to set this up and I have the following in my lua script:
I am not sure of two things:
Thanks! |
Beta Was this translation helpful? Give feedback.
-
There is no pdns.ANAME because it didn't become a standard, you have to ask your provider what # they use for it and put that integer value instead. |
Beta Was this translation helpful? Give feedback.
-
Thank you that helps. I've gotten what I hope is a qtype from DNS Made Easy although they seemed a bit uncertain. That being said when I do a dig instead of seeing the record content I am seeing this:
That record data looks wrong to me. Is this syntactically valid?
I also tried:
I don't see an example of this in the documentation. |
Beta Was this translation helpful? Give feedback.
-
I'm seeing other examples online of record:content() working but my record content should be Is this some ASCII representation or why does it look like this? |
Beta Was this translation helpful? Give feedback.
-
I was told to try qtype 255 then if that didn't work to try qtype 252. The reason for doing this is that DNS Made Easy isn't accepting these ALIAS records. So I'm pretty sure some translation is necessary. Although exactly what qtype to use isn't super clear. |
Beta Was this translation helpful? Give feedback.
-
They are the secondary, we (PowerDNS) are the primary. They're doing a zone transfer FROM us. |
Beta Was this translation helpful? Give feedback.
-
Short description
Right now PowerDNS supports ALIAS records which is fantastic. However, we need to replicate with a secondary provider that doesn't support ALIAS records but instead supports ANAME records (which as best as I can tell are the same thing just with a different name). For reference here's the provider: https://support.dnsmadeeasy.com/support/solutions/articles/47001001412-aname-records
We did find this which is a workaround but it defeats the entire purpose of ALIAS records because then the secondary is just creating A records on their side: https://doc.powerdns.com/authoritative/settings.html#setting-outgoing-axfr-expand-alias
Usecase
We want to be able to use ALIAS records to point the root/apex domain to another DNS name. The issue seems to be competing or potentially different standards. PowerDNS uses the ALIAS record type and a third party provider uses ANAME.
Description
I'd like PowerDNS to support the ANAME record type in addition to the ALIAS record type and their behavior should be the same.
Alternatively a flag to convert ALIAS record types to ANAME record types via the config would also work.
Beta Was this translation helpful? Give feedback.
All reactions