Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

So I have a server at Amazon EC2 running apache2.2 on Linux. I have several "VirtualHosts" running different domains. I am able to access each of the individual sites. My problem, at least I think, is their DNS's aren't being resolved correctly, meaning it takes forever for the site(s) to be found. Once they are located the site(s) perform as expected, but If I were to wait a few minutes and try to retrieve the site once more, it again takes a long time (20+secs) to resolve. This is for production, and not a local development. Note: If I go to to my servers elastic IP ( my default site loads instantly.

Route 53

  NAME: tylerrafferty.com.
  VALUE:  -
  TTL: 60

  NAME: tylerrafferty.com.
  VALUE: 0 smtp.secureserver.net  -  10 mailstore1.secureserver.net
  TTL: 7200

  NAME: tylerrafferty.com.
  VALUE: ns-1043.awsdns-02.org. - ns-1709.awsdns-21.co.uk. - ns-328.awsdns-41.com. - ns-909.awsdns-49.net.
  TTL: 7200

  NAME: tylerrafferty.com.
  VALUE: ns-1043.awsdns-02.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
  TTL: 7200 

  NAME: www.tylerrafferty.com.
  VALUE:  -
  TTL: 7200 
share|improve this question

migrated from serverfault.com Jul 3 '13 at 23:19

This question came from our site for system and network administrators.

There's a disconnect between your perception of a problem and your proposed path to correcting it. A delay in resolving a DNS entity in this scenario occurs somewhere between a client computer, the caching DNS server it points to, and the authoritative DNS server that contains the answer. Nowhere along that path does httpd get involved, as your virtualhosts are not trying to resolve anything. I recommend focusing on the actual problem you see (i.e. show us the DNS query failing). –  Andrew B Jul 3 '13 at 15:41
None of those hostnames appear to exist in the DNS. –  Michael Hampton Jul 3 '13 at 17:10
@Michael Pardon? I can resolve all of them just fine. That did leave to discovering the actual problem though... –  Andrew B Jul 3 '13 at 17:42
@AndrewB You see A or AAAA records for them? All I get is NOERROR... –  Michael Hampton Jul 3 '13 at 17:43
@Michael I can, and +trace works, but something is jacked on these DNS servers. I've elaborated within the answer. –  Andrew B Jul 3 '13 at 18:04

1 Answer 1

up vote 4 down vote accepted

round-robin DNS

Someone has inadvertently created broken round-robin DNS for those DNS records.

$ dig +short www.kyleseetaylor.com
$ dig +short www.vistamechanical.net
$ dig +short www.tylerrafferty.com

The problem you're experiencing is that there's a coin flip chance of getting either IP address as an answer, and people outside of your network cannot reach the 10net address.

(either that or your internal network can't get to the public IP, but the 10net IP is going to break things for everyone on the internet.)

share|improve this answer
Why would my nameserver not return answers to requests for SOA records if I have it set? I am really eager to learn how to correct this problem. What should I read up on or focus on to resolve this issue? –  user180128 Jul 3 '13 at 19:13
Your authority is fine, I ran the SOA query against www. instead of the base domain. Answer has been edited. –  Andrew B Jul 3 '13 at 19:19
After validating your solution it appears you were 100% correct. 10net(10.x.x.x) IP addresses are not routeable over the internet. The coin flip you speak of was a good analogy. Thank you. I've also edited my question as to be more relevant to the solution. Please upvote it if you feel that it can help others solve similar problems. –  user180128 Jul 3 '13 at 22:54

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.