When I query the domain with dig, I get an NXDOMAIN error:
dig fsmax.colmeia.mimic.com.br ... ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25993 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;fsmax.colmeia.mimic.com.br. IN A ;; AUTHORITY SECTION: colmeia.mimic.com.br. 3600 IN SOA ns-1796.awsdns-32.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
Notice that it finishes the answer with the SOA NS: ns-1796.awsdns-32.co.uk.
What baffles me, is that if I ask that NS directly, I actually get the correct answer (the Load Balancer IPs):
dig @ns-1796.awsdns-32.co.uk fsmax.colmeia.mimic.com.br ... ;; ANSWER SECTION: fsmax.colmeia.mimic.com.br. 60 IN A 184.108.40.206 fsmax.colmeia.mimic.com.br. 60 IN A 220.127.116.11 ;; AUTHORITY SECTION: colmeia.mimic.com.br. 300 IN NS ns-1041.awsdns-02.org. colmeia.mimic.com.br. 300 IN NS ns-1796.awsdns-32.co.uk. colmeia.mimic.com.br. 300 IN NS ns-53.awsdns-06.com. colmeia.mimic.com.br. 300 IN NS ns-747.awsdns-29.net.
Something weird is that this was working, and then suddenly after an hour perhaps, it stopped working. I checked if I received an email from domainnameverification, but I haven't.
And I added the relevant entries in my local DNS Provider (Locaweb) so that I forward the DNS resolution of the subdomain (colmeia.mimic.com.br) to AWS Route 53.
Lastly, I checked the DNS Propagation (https://www.whatsmydns.net/#A/fsmax.colmeia.mimic.com.br), and found that the only server that answers correctly is one in Canada.
Any help is greatly appreciated.