Virtual Hosts not working properly

I run a webserver, and we thought we had it set up correctly using linux and BIND. The problem is that we have mutliple domains pointing to vhosts, and for some web surfers (a signifcant number of them, mostly using comcast cable).

URL is the main site for the box

URL
URL
URL

Those are the other domains that point to the Vhosts.

My problem is that most users of ISPs other than comcast can access the domains, and those that are using comcast can't.

our dns are ns1.intudata.com and ns2.intudata.com

If anyone has an ideas please let me know

Thanks in advance
SuperNass

I can access those sites fine, and I'm in the UK.

I retrieved your DNS data as follows:

which all seems correct.

What problem do people on Comcast experience?

They simply can't access the website. For them it's like typing in a total BS url and then getting whatever error, page not found.

I talked to a comcast representative today, he was using comcast and could access all the sites. He says it most likely has to do with the IE DNS timeout issue. When he was going to the urls, he noticed that intudata.com (the main site) resolved slightly faster than the others. So he suggested the IE thing. I don't have comcast either, so next time i can get ahold of someone who has it, if they can't access the urls i'll have them call comcast, and they should be able to walk them through it.

Have you heard of this, does it sound reasonable? secondly if this is the case, is there a way to speed it up, becuase if this is an issue for most comcast customers I can't expect them all to change their settings.


Also as a side note, what is dnsqr? I am always trying to learn, i use Windows and don't know of that command, is it similar to nslookup, or is it another program that is useful?

Thanks

Getting a 404 Page Not Found error implies that their connection to your HTTP server was successful. Are you sure that's the error they got? Or did access attempts just time out?

If it's an issue that only affects Comcast users, then put pressure on Comcast to resolve the issue. There's no "EnableComcastAccess" directive for Apache, so you're going to have to deal with the ISP on this one, rather than fix anything at your end.

It's a tool from djbdns to debug DNS configurations with. It does a similar job to nslookup, only it doesn't suffer from daft design problems.

Sorry, to clarify it's a timeout not a 404. Thanks for your help, i'll contact comcast and see what we can do from there.

Also thanks for the information regarding the DNS tools