Operators: please look in (Domain problem) - Problem solved

[derbyc]

Hi guys! I'm quite new here, although I've been reading posts for a couple of months, this is the first time I post something.

The reason is that my compatriot, Laa-Yosh (I think some of you know him well) asked me to do so, because he cannot reach the Beyond3D domain since the end of October. He exchanged e-mails with his Internet provider and got the next answer (a quick translation): There are registration problems with Beyond3D domain name, please contact with the operator of that domain. That site is not reachable not only from Axelero, but from other providers, too.
Anyway, he is from Hungary and his Internet Provider is Axelero (as it is written in the quoted letter).

May I ask you to check your domain name. Thank you.

 

[Bouncing Zabaglione Bros.]

Suggest you try posting in this in the "site feedback" forum.

Has your friend tried connecting using the IP address (216.180.225.194)? If this works, then the problem is with the ISP not updating their DNS.

 

[derbyc]

Suggest you try posting in this in the "site feedback" forum.

Has your friend tried connecting using the IP address (216.180.225.194)? If this works, then the problem is with the ISP not updating their DNS.

Thanks for both of your tips. I take them and forward the IP part to Laa-Yosh.

 

[MfA]

The website cant be accessed through the IP though it seems, I guess their host routes based on HTTP requests internally (fugly). Is Axelero using some NAT based trickery which might be interacting with B3D's host's trickery perhaps?

 

[Dave Baumann]

B3D is directly accessible via:

http://216.180.225.194/~beyond3d/

 

[Bouncing Zabaglione Bros.]

The website cant be accessed through the IP though it seems, I guess their host routes based on HTTP requests internally (fugly). Is Axelero using some NAT based trickery which might be interacting with B3D's host's trickery perhaps?

Are they using a transparent cache? If so, it could be failing at the cache or the caches IP lookup. The way to test this is to find a third party web proxy and try using that. This could still fail if the ISPs transparent cache is also set up to catch the alternate cache ports (like 8080) and redirect those to the transparent ISPs cache anyway.

Also try running a traceroute to B3D using both the IP and the URL, to see if it is failing at address resolution or somewhere along the path between the ISP and B3D.

 

[Laa-Yosh]

Wee, thanks for the direct address, Dave - I can finally reach the site this way

There seem to be some problems though, font settings and site engine images do not seem to download and the site is generally quite slow.

BZB, I'm not tech savy enough to fully understand what you mean. Tracert for the numeric IP address completes like this:

C:\Documents and Settings\Varga Tamas>tracert 216.180.225.194

Tracing route to 216.180.225.194 over a maximum of 30 hops

  1    31 ms    16 ms    31 ms  lo1.uac0-varosmajor-nrp2.matav.net [145.236.238.
97]
  2    15 ms    16 ms    16 ms  ge1-3-0.core0-ip3.matav.net [145.236.245.65]
  3    16 ms    31 ms    32 ms  dtag-tgn-stm4-if.matav.net [145.236.246.2]
  4   125 ms   141 ms   140 ms  WAS-E4.WAS.US.NET.DTAG.DE [62.154.14.134]
  5   125 ms   141 ms   125 ms  so-4-2-2.mpr1.iad10.us.above.net [64.125.12.73]

  6   125 ms   141 ms   140 ms  so-4-0-0.mpr1.iad2.us.above.net [64.125.30.118]

  7   125 ms   141 ms   140 ms  so-4-0-0.cr2.iad1.us.above.net [209.249.0.133]
  8   125 ms   141 ms   140 ms  so-0-0-0.cr1.iad1.us.above.net [208.185.0.109]
  9   125 ms   140 ms   141 ms  so-1-0-0.cr1.dca2.us.above.net [208.184.233.125]

 10   141 ms   172 ms   234 ms  pos0-0.pr1.atl4.us.above.net [208.185.0.230]
 11   141 ms   234 ms   250 ms  64.124.17.5.gnax.net [64.124.17.5]
 12   141 ms   156 ms   141 ms  209.51.131.58
 13   156 ms   141 ms   140 ms  216.180.225.194

Trace complete.

For www.beyond3d.com though, I get only this:

Unable to resolve target system name [url]www.beyond3d.com[/url].

I'll also try to direct the ISP's sys admins here to take a look.

And thanks for the help

 

[derbyc]

This message

Unable to resolve target system name [url]www.beyond3d.com[/url].

seems to refer a DNS problem. How do you get your DNS configuration (automatically or manually)? If manually, try mine: 194.149.0.157 (primary), 194.149.0.156 (secondary).

 

[Laa-Yosh]

This seems to work. Thanks

 

[Bouncing Zabaglione Bros.]

For www.beyond3d.com though, I get only this:

Unable to resolve target system name [url]www.beyond3d.com[/url].

I'll also try to direct the ISP's sys admins here to take a look.

And thanks for the help

As per my first post, and the fact you can access via the IP address, this points directly to the DNS at your ISP not having been correctly updated. When your browser contacts your ISP's DNS server to find out what the IP address of B3D is (so that you can send your packets to the right place), your ISPs DNS is shrugging it's shoulders and saying it doesn't know the address. What it *should* do in this case is ask the upstream DNS servers, if necessary chaining all the way back up to the master DNS servers for the whole world until one of the DNS servers has the B3D IP address cached and can send it back.

You could be using hard coded DNS addresses rather than DHCP, and the IPs may have changed, but then you would't be able to access anything.

The only other (small) possibility is that you have messed about with your system and misconfigured your DNS, either a local one that isn't working, or broken timout settings for failed lookups in the built-in WindowsXP cache (ie not timing out failed DNS entries in the local cache).

 

[Gubbi]

For www.beyond3d.com though, I get only this:

Unable to resolve target system name [url]www.beyond3d.com[/url].

I'll also try to direct the ISP's sys admins here to take a look.

And thanks for the help

As per my first post, and the fact you can access via the IP address, this points directly to the DNS at your ISP not having been correctly updated. When your browser contacts your ISP's DNS server to find out what the IP address of B3D is (so that you can send your packets to the right place), your ISPs DNS is shrugging it's shoulders and saying it doesn't know the address. What it *should* do in this case is ask the upstream DNS servers, if necessary chaining all the way back up to the master DNS servers for the whole world until one of the DNS servers has the B3D IP address cached and can send it back.

What it should do is ask the com. root servers for the Name Server (NS) record for the beyond3d.com zone. It should then find out that:

beyond3d.com nameserver = ns1.beyond3d.com
beyond3d.com nameserver = ns2.beyond3d.com
ns1.beyond3d.com internet address = 216.180.225.195
ns2.beyond3d.com internet address = 216.180.225.196

Then it should ask ns1.beyond3d.com for the A record for www.beyond3d.com, which will yield:

Name: beyond3d.com
Address: 216.180.225.194
Aliases: www.beyond3d.com

There's nothing weird about the beyond3d.com Source Of Authority record (SOA):
beyond3d.com
primary name server = ns1.beyond3d.com
responsible mail addr = baumd.clara.co.uk
serial = 1032618732
refresh = 28800 (8 hours)
retry = 7200 (2 hours)
expire = 3600000 (41 days 16 hours)
default TTL = 86400 (1 day)
beyond3d.com nameserver = ns2.beyond3d.com
beyond3d.com nameserver = ns1.beyond3d.com

TTL and refresh are both low enough that any sane caching nameserver would pick up any changes quickly. One can nit pick at the serial number, it is normal practice to use a yyyymmddxx format for the serial number but as long as it increases on every change it shouldn't be a problem.

My guess is Laa-Yosh is using Windows XP/2K and hasn't disabled the horribly broken DNS client service in there. If it still doesn't work after disabling that, try to find another DNS server to use instead of the one you currently are using. -Or build your own Linux/BSD box and run bind as a caching DNS on it.

Cheers
Gubbi