Web Hosting Talk : Web Hosting Main Forums : Hosting Security and Technology : Random DNS? issue I cant troubleshoot

[pj1s]

I help run a production music site beat.org.

All our audio is on the subdomain audio.ibeat.org.

Everyone can access ibeat.org - but a few (not me) cannot access audio.ibeat.org - which times out. The subdomain is run on same server, IP, DNS and so on... A typical LAMP setup btw.

What could possibly be doing this.

My hope is to find a fellow WHTer that actually has this problem, and would help me troubleshoot.

[040Hosting]

Just some idea's everything seems to work from here as well:

- DNS of these users is not updated yet; ask them to use opendns.com to test.
(make sure they issue a ipconfig /flushdns and restart their browser if they are willing to try this.)
- Did you Block IP ranges in a .htaccess file for the audio.ibeat.org ?

[pj1s]

Thank you 040Hosting

I've asked a few to try out OpenDNS - but they haven't replied back. Hopefully that would be it. OpenDNS cache check matches as it should. Rather annoying for users though, if they have to change their settings.

We are blocking a range of chinese IPs (go figure!) that were hammering us... but that should'nt be it. But a good idea to check out non the less... hadn't thought of it.

I'll get one to try a flush.

[040Hosting]

Originally Posted by pj1s

Thank you 040Hosting

I've asked a few to try out OpenDNS - but they haven't replied back. Hopefully that would be it. OpenDNS cache check matches as it should. Rather annoying for users though, if they have to change their settings.

They should not need too, but it at least shows you where the issue is located; if it works you know some of your user-base have slow or not updating nameservers (we have seen these many times before).

Hope you will find the problem soon.

[lamerfreak]

I'm not 100% sure, but there's a sort of problem in DNS... but I'd expect the whole domain to be inaccessible to some.

ns1 and ns2.lostaudio.com exist at the roots, but the nameservers themselves don't have A records in their own configurations.

AFAIK, this will fail logic checks in some resolvers. Might want to get that corrected anyway and see if it solves the other problem.

[speculatrix]

if using BIND as a name server, there are gotchas which manifested , you have to explicitly delegate subdomain audio.ibeat.org in the ibeat.org domain to make it work. this used to not be the case IIRC.