Route53 DNS problems about ingress-nginx HOT 6 CLOSED

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from ingress-nginx.

/retitle Route53 DNS problems
/remove-kind bug
/kind support

from ingress-nginx.

Hi @longwuyuan and @strongjz
can you help me on this problem it is very critical , so please help me on this .

from ingress-nginx.

Your issue description is not showing any problem with the ingress-nginx controller because routing and TLS works for all users.

So what is the problem with the ingress-nginx controller when you say this below

After adding SSL to my NGINX ingress controller, whenever I hit abc.com, I am able to access the application, but it forwards the site from abc.com to qwe.com, and I see qwe.com in the browser.

I suggest ;

• Click the new-bug report button and see the questions asked in the template there
• Edit your issue-description and remove all the imaginary hypothetical info
• Answer all the questions asked in the new bug report template in the issue description
• Ensure that you provide the information formatted in markdown
• Incluse the kubectl describe output for all the related resources
• Include the curl commands and outputs with -v
• Include the logs of the ingress-nginx controller
• Refer the output of the curl command output to state the unexpected response
• Mock write the response you expect to the curl command you executed

My guess is that you are not reporting any problem in the ingress-nginx controller code. It is very likely you are referring to some kind of application design or platform design related problem, and the ingress-nginx controller is a component.

You are confusing readers here by first saying that you are yourself likely having a CNAME record that is doing is causing some redirection here

So, when I hit abc.com, it routes like this: abc.com -> Route 53 -> API Gateway -> Ingress Host (qwe.com) -> Backend Service.

And then you are sort of claiming that you DO NOT expect the redirection via CNAME here

Whenever I hit abc.com, I should get a response on abc.com only, 

If you are trying to solve a problem that is NOT in the ingress-nginx controller code but somewhere in your DNS or application/platform design, then you have better chances to discuss this in the kubernetes-users channel of the K8S slack. There are more users & experts there, when compared to limited resources here.

from ingress-nginx.

Since there is no evident problem to work on in the ingress-nginx controller scope, I will close this issue for now.

Feel free to re-open the issue after you have posted the information that shows a problem that the project needs to solve in the ingress-nginx controller.

/close

from ingress-nginx.

@longwuyuan: Closing this issue.

from ingress-nginx.