DNS_PROBE_FINISHED_NXDOMAIN error occurred when configuring two DNSs with the same ELB in your name .com.
The configuration is like setting the ACM on the ELB and hanging one EC2 under it.
DNS name for ELB: elb Name - xxxxxxxxx.ap-northeast-1.elb.amazonaws.com
Route 53 is not used and
We set the DNS record with the following DNS name as com.
DNS record settings in .com
The first release only runs a subdomain called sub1 and
I released the service and it was running without any problems.
Since it was running steadily, the next improvement is
We have decided to deploy services for specific users by dividing subdomains.
Therefore, after configuring the subdomain named sub2 with the name .com,
I released a service called
However, from then on,
for subdomains of sub2 DNS_PROBE_FINISHED_NXDOMAIN error has occurred.
At the same time, the above error is not for all users, but for some users (all users who have received previous inquiries tend to be Window users)
is the only one that has an error and not everyone can see it.
[Setting in com]
sub1.example.com CNAME3600elb Name - xxxxxxxxx.ap-northeast-1.elb.amazonaws.com sub2.example.com CNAME3600elb Name - xxxxxxxxx.ap-northeast-1.elb.amazonaws.com
Therefore, I am troubled because I do not know the cause.
I tried various things and asked your name com.
Could you please let me know if you can find any information that can give me a hint?
dig CNAME sub2.example.com ; <>>DiG 9.8.3-P1<>CNAME sub2.example.com. ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<-opcode:QUERY, status: NOERROR, id:33436 ;; flags:qrrdra;QUERY:1, ANSWER:1, AUTHORITY:0, ADDITIONAL:0 ;; QUESTION SECTION: ;elb Name - xxxxxxxxx.ap-northeast-1.elb.amazonaws.com.INCNAME ;; ANSWER SECTION: sub2.example.com.3599 INCNAME elb Name - xxxxxxxxx.ap-northeast-1.elb.amazonaws.com. ;; Query time—110 msec ;; SERVER: xxx.xxx.x.x#53 (xxx.xxx.x.x) ;; MSG SIZE rcvd—107
Thank you for your cooperation.
I don't want to be as responsive to end users as possible because it's for B2C.
Is there a possibility that this kind of thing will solve the problem?
Clear DNS Cache
The first thing that comes to mind is the effect of the browser cache, but if you want to keep in touch with the problematic PC in Chrome's Guest Mode, you should try clearing the browser cache.
Read and add comments
DNS_PROBE_FINISHED_NXDOMAIN seems to be a problem with the client environment, so you may find out if DNS name resolution is successful in the browser, OS, and network layers of the client environment.
It seems that the browser has already been verified, so why don't you try clearing the cache at the OS level?However, if it's the same on multiple PCs, you might want to check if there's any DNS cache on the network.
In my experience, it was cured after clearing the DNS cache of the router in the user environment.
369 Update Flask User Information
353 I want to create an array of sequences from "1" to a specified number.
355 Unity Virtual Stick Does Not Return to Center When You Release Your Finger
366 Is there any other way to save the Python database?
362 To Limit Column Values to Strings in a String List Using sqlalchemy
© 2023 OneMinuteCode. All rights reserved.