2 Answers
- Newest
- Most votes
- Most comments
1
Hello.
From my network, name resolution appears to be working properly.
Is there a possibility that there is a problem with your local network's DNS settings?
dig app.mergetemps.com
; <<>> DiG 9.16.1-Ubuntu <<>> app.mergetemps.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38580
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;app.mergetemps.com. IN A
;; ANSWER SECTION:
app.mergetemps.com. 60 IN A 3.104.183.68
app.mergetemps.com. 60 IN A 13.237.127.47
;; Query time: 163 msec
;; SERVER: 192.168.11.1#53(192.168.11.1)
;; WHEN: Tue Jan 30 16:43:51 JST 2024
;; MSG SIZE rcvd: 79
1
I can resolve your domain and sub-domain from any third party domain tool box like [1][2][3]
I checked that your NS records are normal and work properly. It's suggest you check the DNS configuration of the local network like static rule in /etc/hosts
or contact the administrator of local dns resolver to further confirm whether they have an overwrite or customer forwarding rule for this domain.
[1] https://toolbox.googleapps.com/apps/dig/
answered 3 months ago
Relevant content
- asked 2 months ago
- asked 6 months ago
- Accepted Answerasked 9 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
It started working on local network the next day. Not sure what happened though @Riku_Kobayashi