-
Notifications
You must be signed in to change notification settings - Fork 72
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
Resource: infoblox_cname_record by default appending zone information to alias record #60
Comments
Hi,
I'm off next week will tell the team to look into this
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: elangoganesan <notifications@github.com>
Sent: Saturday, February 15, 2020 1:21:06 AM
To: infobloxopen/terraform-provider-infoblox <terraform-provider-infoblox@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [infobloxopen/terraform-provider-infoblox] Resource: infoblox_cname_record by default appending zone information to alias record (#60)
We are trying to register DNS Names for AWS ELB in our infoblox environment with a CNAME mapping to our internal domain . The plugin is registering the CNAME successfully how ever it is making the assumption that canonical name is in the same zone as alias record . This is causing issues in resolving the CNAME record correctly .
Output for DNS Lookup After Registration:
nslookup myapp.exampledomain.com
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
myapp.exampledomain.com canonical name =myapp-xdsd134.elb.us-east-1.amazonaws.com**.exampledomain.com**
In Looking at the code , seems like we are assuming that both canonical name and alias record are in the same zone . This makes it impossible to use this plugin in cloud deployments.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/infobloxopen/terraform-provider-infoblox/issues/60?email_source=notifications&email_token=AIU4JIQSZGWRXNZK2MHLTPLRC3Y2VA5CNFSM4KVOUOC2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4INVHMWQ__;!!JYsgTRAg6ZQ!dUKIS-ZABxXkLfff7E0Asd2eUJHe19-VfJsicTwWwhy-9hDW-NXOqoSGYX15EJk9$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AIU4JIV3KYXXL2YECPPF7IDRC3Y2VANCNFSM4KVOUOCQ__;!!JYsgTRAg6ZQ!dUKIS-ZABxXkLfff7E0Asd2eUJHe19-VfJsicTwWwhy-9hDW-NXOqoSGYRU1O-wp$>.
|
closing this as per the above PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are trying to register DNS Names for AWS ELB in our infoblox environment with a CNAME mapping to our internal domain . The plugin is registering the CNAME successfully how ever it is making the assumption that canonical name is in the same zone as alias record . This is causing issues in resolving the CNAME record correctly .
Output for DNS Lookup After Registration:
Non-authoritative answer:
myapp.exampledomain.com canonical name =myapp-xdsd134.elb.us-east-1.amazonaws.com**.exampledomain.com**
In Looking at the code , seems like we are assuming that both canonical name and alias record are in the same zone . This makes it impossible to use this plugin in cloud deployments.
The text was updated successfully, but these errors were encountered: