Forums.utassault.net

  • Hey - turns out IRC is out and something a little more modern has taken it's place... A little thing called Discord!

    Join our community @ https://discord.gg/JuaSzXBZrk for a pick-up game, or just to rekindle with fellow community members.

Shinon`

Shinon`

19x sshot!
Aug 21, 2002
5,910
0
Sprang-Capelle, NL
why takes it so long to get to this forum?
i have to refresh 5/6 times before it comes up (no matter what machine).
Is there another link or something, because this is getting fucking annoying.
 
Shinon` said:
why takes it so long to get to this forum?
i have to refresh 5/6 times before it comes up (no matter what machine).
Is there another link or something, because this is getting fucking annoying.
Click to expand...
I've got the same 'problem' at home, for some reason it bounces the request for 4 or 5 times. That's the same for IRC, btw. No clue why though!
 
Hrm interesting.

Could people who've got problems do a ping -n 100 forums.utassault.net and paste the summary results? I want to know if you've got packet loss.

I had a similar problem to the web host and for some reason some requests were getting dropped

I just want to see this bit (if you got problems)
Code: 
Ping statistics for 80.194.247.166:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum = 126ms, Average = 58ms
 
Ping statistics for 80.194.247.166:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 52ms, Average = 36ms

Weirdly enough, the last 2 days it stopped giving me errors :lol:
I guess complaining works :sofa:
 
Right, first off, the pinging:
Code: 
Ping-statistieken voor 80.194.247.166:
    Pakketten: verzonden = 100, ontvangen = 99, verloren = 1
    (1% verlies).De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
    Minimum = 40ms, Maximum = 91ms, Gemiddelde = 45ms

Nothing really wrong there.
Using nslookup, i get the following results:

Code: 
> utassault.net
Server:  dsldevice.lan
Address:  192.168.2.254

Non-authoritative answer:
Name:    utassault.net
Address:  80.194.247.166

> utassault.net
Server:  dsldevice.lan
Address:  192.168.2.254

[B]*** dsldevice.lan can't find utassault.net: Server failed[/B]
> utassault.net
Server:  dsldevice.lan
Address:  192.168.2.254

[B]*** dsldevice.lan can't find utassault.net: Server failed[/B]
> utassault.net
Server:  dsldevice.lan
Address:  192.168.2.254

[B]*** dsldevice.lan can't find utassault.net: Server failed[/B]
> utassault.net
Server:  dsldevice.lan
Address:  192.168.2.254

Non-authoritative answer:
Name:    utassault.net
Address:  80.194.247.166

So basically this means thatthe DNS server is running, but not working properly. Corrupted packages?
 
I never have problems connecting to utassault.net, not here nor at work.
Infact, I always use utassault to see if internet works because it loads instantly :D
 
deadly said:
Right, first off, the pinging:
Code: 
Ping-statistieken voor 80.194.247.166:
    Pakketten: verzonden = 100, ontvangen = 99, verloren = 1
    (1% verlies).De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
    Minimum = 40ms, Maximum = 91ms, Gemiddelde = 45ms

Nothing really wrong there.
Using nslookup, i get the following results:

Code: 
> utassault.net
Server:  dsldevice.lan
Address:  192.168.2.254

Non-authoritative answer:
Name:    utassault.net
Address:  80.194.247.166

> utassault.net
Server:  dsldevice.lan
Address:  192.168.2.254

[B]*** dsldevice.lan can't find utassault.net: Server failed[/B]
> utassault.net
Server:  dsldevice.lan
Address:  192.168.2.254

[B]*** dsldevice.lan can't find utassault.net: Server failed[/B]
> utassault.net
Server:  dsldevice.lan
Address:  192.168.2.254

[B]*** dsldevice.lan can't find utassault.net: Server failed[/B]
> utassault.net
Server:  dsldevice.lan
Address:  192.168.2.254

Non-authoritative answer:
Name:    utassault.net
Address:  80.194.247.166

So basically this means thatthe DNS server is running, but not working properly. Corrupted packages?
Click to expand...

?

Corrupted packages?!
 
according to deadly's log:
Your local adsl router/ whatever has it's own DNS Server, which acts as a sort of cache between your pc(s) and the outside world. Basicly, if it returned an answer the first time, you would expect it to give an answer the second time as well. (Cached). So it looks like your local router is giving the problem (in this case anyhow). Did you try giving it a reboot?

Or am i wrong on this?

Also your browser caches the dns request/ response so as long as it works 1 time, it'll work..
 
doh said:
?

Corrupted packages?!
Click to expand...

:confused:

The following message generally means that the DNS server is running, but is not working properly. For example, it might include a corrupted packet, or the zone in which you are querying for a record might be paused. However, this message can also be returned if the client queries for a host in a domain for which the DNS server is not authoritative and the DNS server cannot contact its root servers, or is not connected to the Internet, or has no root hints.

*** < Server > can't find < Name or IP address queried for >: Server failed.
Click to expand...
 
So you mean corrupted packets? Theres a major difference there. Besides when its working for 371309 domains (everydns.net), its clearly not sending out corrupted packets, but rather your connection corrupting packets, or your router.
 
doh said:
So you mean corrupted packets? Theres a major difference there. Besides when its working for 371309 domains (everydns.net), its clearly not sending out corrupted packets, but rather your connection corrupting packets, or your router.
Click to expand...

doh............ :D

that it's working for 371095423568411356 domains doesn't mean it isn't perfect though :P ... But anyhow, Deadly you tried rebooting your router?
 
Rel@x said:
doh............ :D

that it's working for 371095423568411356 domains doesn't mean it isn't perfect though :P ... But anyhow, Deadly you tried rebooting your router?
Click to expand...

Perhaps, but i highly doubt that they're too noobish to set up a "non-packet corrupting" DNS server with that many domains.
 
You must log in or register to reply here.
Top Bottom
Back