I recently got a new domain (lets call it testdomain.extample) from Route53 on Amazon. I further have a classic load balancer from AWS that I want requests to be forwarded to when somebody visits www.testdomain.example.
Under hosted zones on Route53 I went over instructions to set NS, SOA (Amazon adds a bunch of ns-xxx.* hostnames for NS and one for SOA). I also added an A type record and added my load balancer (from a dropdown) to it as specified in the documentation.
When I run dig on my domain this is what I see (I don't see an answer section as I see for other working websites). It is about 12 hours since I updated on AWS. The browser shows "server IP address could not be found." error. Is there something I am missing in all of this?
>>> dig www.mytestdomain.example
; <<>> DiG 9.10.6 <<>> www.mytestdomain.example
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 3567
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.mytestdomain.example. IN A
;; Query time: 161 msec
;; SERVER: 192.0.2.75#53(192.0.2.75)
;; WHEN: Tue Apr 23 05:44:21 PDT 2019
;; MSG SIZE rcvd: 52
Best Answer
There is no answer section because your query went unanswered,
check the status section: the name server returned an error code and you get the SERVFAIL error response. That is typically the result of a nameserver or your zone not having been configured correctly.
Note: In many cases it may be necessary to know the actual domain name in order to answer DNS questions. See What information should I include or obfuscate in my posts?