[WXC/VFX] Xnet DNS issue?

Forums › One New Zealand (including Vodafone, WxC, Farmside) › [WXC/VFX] Xnet DNS issue?

bradi

137 posts

Master Geek
Inactive user

#30333 4-Feb-2009 22:03

Is anybody but me having problems with Xnet's DNS servers? I have them hard coded as per their helpdesk page :

Primary DNS: ns1.xnet.co.nz or 58.28.4.2

Secondary DNS:ns2.xnet.co.nz or 58.28.6.2

I did notice a Chorus van across the road this morning... /me sighes but can't see how they could possibly effect Xnet's DNS servers...

===

H:\>tracert ns1.xnet.co.nz
Tracing route to ns1.xnet.co.nz [58.28.4.2]
over a maximum of 30 hops:
1    <1 ms    <1 ms    <1 ms dslrtr-1.home.megacityone.net.nz [192.168.1.1]
2    10 ms     9 ms     9 ms ip-58-28-15-31.wxnz.net [58.28.15.31]
3     9 ms    10 ms    10 ms 58.28.13.83
4     9 ms    12 ms     9 ms 58.28.8.3
5     *        *       10 ms ge-0-0-1-akl-fw01.wxnz.net [58.28.160.2]
6     *        *       10 ms ns1.wxnz.net [58.28.4.2]
Trace complete.

H:\>ping ns1.xnet.co.nz
Pinging ns1.xnet.co.nz [58.28.4.2] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 58.28.4.2: bytes=32 time=9ms TTL=59
Request timed out.

Ping statistics for 58.28.4.2:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
    Minimum = 9ms, Maximum = 9ms, Average = 9ms

H:\>tracert ns2.xnet.co.nz
Tracing route to ns2.xnet.co.nz [58.28.6.2]
over a maximum of 30 hops:
1     1 ms    <1 ms     1 ms dslrtr-1.home.megacityone.net.nz [192.168.1.1]
2    12 ms    10 ms    10 ms ip-58-28-15-31.wxnz.net [58.28.15.31]
3    11 ms    11 ms     9 ms ip-58-28-13-83.wxnz.net [58.28.13.83]
4    10 ms     9 ms    11 ms 58.28.8.3
5     *        *        *     Request timed out.
6     *       10 ms     9 ms ns2.wxnz.net [58.28.6.2]
Trace complete.

H:\>ping ns2.xnet.co.nz
Pinging ns2.xnet.co.nz [58.28.6.2] with 32 bytes of data:
Reply from 58.28.6.2: bytes=32 time=9ms TTL=59
Request timed out.
Request timed out.
Reply from 58.28.6.2: bytes=32 time=10ms TTL=59
Ping statistics for 58.28.6.2:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 9ms, Maximum = 10ms, Average = 9ms

1 | 2

70 posts

Master Geek

#194128 4-Feb-2009 22:13

Like you wouldn't believe., google will load, google won't load. msn will sign in, msn won't sign in. When stuff does load it's slower than a 56 k modem would be.

PAINFUL..

Glad I'm not alone. Maybe the others can't get on to complain..

CYaBro

4583 posts

Uber Geek

ID Verified

Trusted

#194136 4-Feb-2009 22:35

No problems for me here on Xnet.

Opinions are my own and not the views of my employer.

bradi

137 posts

Master Geek
Inactive user

#194137 4-Feb-2009 22:40

@CYaBro
ok, well that's strange... I would have thought that packet loss would be a problem for all Xnet users.

Can I ask what DNS servers you using?
What are pings / tracerts to the DNS servers like?

richms

28169 posts

Uber Geek

Trusted

Lifetime subscriber

#194148 4-Feb-2009 23:19

I called mum from a mates place today to try to get her to find the vodafone/ihug dialup number so that my friend could dialup on my get3 account till orcon get his dsl provisioned - anyway, things were not loading at all, even google came back not found - but msn was working just fine, so it may coincide with the time that you had the problems - about 2-3pm I would say, possibly a bit later then that.

Good thing the nice neighbour was kind enough to be operating a public hotspot so we could get on and find it, but with that available there is little reason to get the dialup number.

Richard rich.ms

exportgoldman

1202 posts

Uber Geek

Trusted

#194153 4-Feb-2009 23:44

I've been having weird problems all night, but I just installed a new laptop with Windows 7 (I have another two machines working at home with Win7) and thought it was just a problem with that.

I find the first DNS request seems to fail/timeout etc but the second try works fine.

Tyler - Parnell Geek - iPhone 3G - Lenovo X301 - Kaseya - Great Western Steak House, these are some of my favourite things.

Niel

3267 posts

Uber Geek

Trusted

#194157 5-Feb-2009 06:01

No problem at all, except my modem locked up once last night which happens every 1 to 2 weeks.

You can never have enough Volvos!

BlakJak

1275 posts

Uber Geek

Trusted

#194223 5-Feb-2009 10:55

I nearly posted last night but didnt as it seemed to 'come right'.
Their DNS was crap last night. I got home about 8pm and had no DNS service at all from Xnets NS until nearly 11 by which time i was heading for bed.
Was only able to surf at all by manually specifiying third party NS in my boxen.

Tested from outside of Xnet I was also seeing poor reliability, so i nail DNS entirely for the problem; i've noticed there's been lots of DNS delays with Xnet (slow to resolve web addresses) which is negatively impacting on performance, despite HTTP requests themselves often working fine once the address has resolved.

Oh and nice that their helpdesk shut at 8... :\

No signature to see here, move along...

Tradepub

Free professional, reference and technical white papers (affiliate link).

BigFella

105 posts

Master Geek

#194249 5-Feb-2009 12:48

BlakJak: i've noticed there's been lots of DNS delays with Xnet (slow to resolve web addresses) which is negatively impacting on performance, despite HTTP requests themselves often working fine once the address has resolved.

Ditto - it got bad enough that I switched to opendns.com, which did improve the situation.

pistolpower

139 posts

Master Geek

#194325 5-Feb-2009 17:16

I have been having problems with loading web pages recently too. I occasionally get one of those "Page not loading" messages when I try loading a webpage. I do not think I was having this problem before Feburary. If something is happending with the xnet DNS servers that would explain why occasionally my web pages do not load.

gizmoguy

7 posts

Wannabe Geek

#194326 5-Feb-2009 17:55

Interesting, I've had no issues resolving DNS with the Xnet DNS servers lately.

In saying that I've just tested and are seeing packet loss to ns1.xnet.co.nz and ns2.xnet.co.nz currently:

--- ns1.xnet.co.nz ping statistics ---
75 packets transmitted, 71 packets received, 5% packet loss

Tested twice to make sure:

--- ns1.xnet.co.nz ping statistics ---
76 packets transmitted, 67 packets received, 11% packet loss

Whereas seeing no packet loss to xnet.co.nz:

--- xnet.co.nz ping statistics ---
68 packets transmitted, 68 packets received, 0% packet loss

I do run a caching DNS server here on my network so maybe thats caching the good results so I don't have problems resolving addresses that have been cached.

bradi

137 posts

Master Geek
Inactive user

#194328 5-Feb-2009 18:19

Seems to have come right now...

not holding my breath to see if Xnet post something to explain.... gonna leave the 3rd party NS entries in my DNS Server for a while tho :p

BlakJak

1275 posts

Uber Geek

Trusted

#194332 5-Feb-2009 18:37

I sent an email to helpdesk about it, we'll see if I get much of a response. However it's fine tonight...

No signature to see here, move along...

xlinknz

1127 posts

Uber Geek

Trusted

#194727 8-Feb-2009 12:33

Yes I concur I have been experiencing infrequent packet loss [ping timeouts] on both Xnet DNS severs the last couple of days but no such issue on the OpenDNS servers

There is definately something going wrong with their [Xnet] DNS servers maybe intermittant DOS attack ?

I hope this does not go on and they get it resolved ASAP and not take for ever like they did with their recent severe mail problems. I call them Monday

bradi

137 posts

Master Geek
Inactive user

#194768 8-Feb-2009 19:22

Still the same here... intermittant DNS probs for the last few days... annoying but not a major... DDOS?

http://isc.sans.org/diary.html?storyid=5713
http://isc.sans.org/diary.html?storyid=5773&rss

pistolpower

139 posts

Master Geek

#194797 8-Feb-2009 20:55

Lol yer I am still having the same problem with the dns servers timing out on me. Probably part of one of their "cost-reduction-schemes" and "profit maximisation schemes" that have resulted in them ceasing to increase supply of dns server capactiy as old dns server stuff breaks and as new customers join and demmand increases. Wonder what else they are skimping on.

And the more we use their services the more we pay them. The more we use it the more it costs them. As we use it they make profit because we pay MORE than it costs them to SUPPLY their service to us. So the more we use it, the more we pay them, the more they profit, the more infastructure is needed to supply us.

How hard is it to keep up with demmand when we use more.

1 | 2