Forum Moderators: phranque

Message Too Old, No Replies

DNS errors

Help with some tricky dns errors!

         

ahmedtheking

10:00 am on Aug 29, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Ok, this is going to be difficult to explain without me posting urls. I wont post any yet, only when i have clearence (please?).

The problem is, i have lotsa websites on this webserver, eg snipped. But some people (using Wanadoo on windows) cannot see the sites. However, if they go straight through the IP path address, snipped they can see the site.

I thought ok fair enough, but none of my sites are relativly linked and all are done in PHP.

I have access to the DNS functions of each site that I host (through a reseller account in WHM). Is there anything I can do to fix this problem? Or my hosts can do?

Check this out, snipped

that is a DNS report of one of my sites, how can i/my webhosts fix those errors?

(sorry if i have posted urls again, but i need them for this question! I did not post the full urls!)

[edited by: DaveAtIFG at 2:23 pm (utc) on Aug. 29, 2004]

MattyMoose

4:14 pm on Aug 30, 2004 (gmt 0)

10+ Year Member




Check this out, snipped

Maybe you could obfuscate the error, or whatever it was that you posted. change IP addresses to non-existant ranges, and change domain names to yoursite.com or something.

Can't do anything until we see errors. ;)

-MM

ahmedtheking

6:03 pm on Aug 30, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Ok, erm...

The error that they recieve is as follows:

Gateway Timeout
The following error occurred:
[code=DNS_TIMEOUT] A DNS lookup error occurred because the request timed out during the lookup.

- ends -

Erm, any more info needed?

DaveAtIFG

7:06 pm on Aug 30, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



using Wanadoo on windows
I'm not familiar but a quick search leads me to think Wanadoo is a popular French ISP. If so, and everyone else can connect to your site, Wanadoo has the problem, perhaps with their name server or name server caches... If they provide a custom browser perhaps it isn't yet HTTP 1.1 compatible and can't handle virtual hosting... Or some users need to update their browser.

mcavic

11:56 pm on Aug 30, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Sounds like a problem with Wanadoo's DNS servers. I'd send the url to them and tell them that some of their users aren't able to access it.

I have seen another case where an ISP's DNS server (in the US) was unable to look up one specific Canadian host.

If it was a problem with name virtual hosting, the user should get the wrong page, instead of no page at all.

ahmedtheking

10:47 am on Aug 31, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I contacted them but they didn't have any of it! Ill try again! Thanks for the help guys (and gals, if any?)