I currently host a TinyDNS server that serves DNS requests for all domains with nameservers that point to the server. The data configuration file is:
with 220.127.116.11 being the IP of the server. It's intended to be a wildcard DNS server (any nameserver that points to this server will return A records that point to itself).
However, DNS lookups have been really slow for these domains when attempting to access the website on the domain and I have been experiencing this on different devices and networks (sometimes up to 10 seconds). Are the DNS records that are propagating from my DNS server somehow malformed? Here is an example domain: http://trp.do/s/
I know it's a DNS issue and not a website issue by inserting various headers with timestamps at different points within the request and response stack. They are within
ms whereas the actual request from start to finish is around 5-10 seconds. When using Google Chrome, it appears to be stuck on "Resolving Host" on the bottom left as well. I've dug deeper and used Rack-Mini-Profiler @ https://github.com/MiniProfiler/rack-mini-profiler to profile the requests and listed Domain Lookup in the range of 5-10 seconds as well. So that's why I'm fairly confident it's a DNS issue and not a website performance issue.
Addressing the concerns of the single point of failure, I'm aware of it but don't think it should be affecting performance on a consistent level.
My burning question is... can a malformed DNS record even cause a situation like this?