-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FEATURE REQUEST: Handle "unknown" DNS record types #2432
Comments
Really great to see this. I was running into this problem trying to manage a local instance of Technitium DNS with AXFR+DDNS. Technitium uses its own "App" records for basically any nonstandard DNS behavior (e.g, split-horizon records, or randomizing the order of records for round-robin load balancing), but it will also happily sync these records to another Technitium server by sending them over AXFR. But then such suspect records existing trip up DNSControl, even with Really my point is, I'd like to at least see this work with the AXFR+DDNS provider! Thank you for the awesome software! |
@b- Please try it with an "app" record and see if there's any improvement. |
Ah! That's an interesting edge case! I don't have an ibeep account. Is there a way you can help me reproduce this? |
Ibeep.com is my domain! I'm just using Technitium DNS -- I have VMs running it at tdns1.ibeep.com and tdns2.ibeep.com. I'm wondering the easiest way for you to reproduce this. I suppose I could share a TSIG key over a secure channel, or something? Or probably better if you could just install Technitium DNS somewhere and create a zone and a record as I showed in the screenshot -- it's pretty much a point-and-click web interface that runs on Windows and Linux, so it shouldn't be too difficult. (I'm using an Ubuntu VM on a home Proxmox server and also on an Oracle free-tier VM) |
Oops.. I mean I don't have a Technitium DNS account. Sorry! It might be easier for me to set up a branch with extra debug info. You could run it and send me the output. Let me think about it! |
I've split this out to a separate issue: #2805 |
Is your feature request related to a problem? Please describe.
When a vendor supports a DNS record type (either proprietary, standard, or pre-standard), DNSControl frequently panics or errors out.
Describe the solution you'd like
DNSControl should have a record type called "UNKNOWN" which holds the information downloaded from the provider.
Describe alternatives you've considered
The alternative is to manually delete these records so that DNSControl doesn't see them.
Additional context
The text was updated successfully, but these errors were encountered: