Mweb Internal Network DNS Issues

W

Waste

Well-Known Member
Joined
Oct 22, 2006
Messages
233
Reaction score
7
Location
Bloemfontein
Just wanted to see if more people are experiencing problems on the Mweb network regarding DNS resolution. We have an Virtual Server with them, and DNS is not resolving from the server itself, thought from outside (like from my laptop, it is working).

This is affecting a lot of our services as we use DNS to point to different parts of our hosted services.

This all started this morning (I have reports from 6h30).

We are contacting Mweb to ask for assistance, so I am just spreading the word if someone else is affected.

Update:
My server is querying the DNS server: "vh-dns-01.vm.mweb.net" and it is timing out.
 
Last edited:
Ping & Tracert (I use Neotel)


Pinging vh-dns-01.vm.mweb.net [41.86.97.240] with 32 bytes of data:
Reply from 41.86.97.240: bytes=32 time=83ms TTL=51
Reply from 41.86.97.240: bytes=32 time=64ms TTL=51
Reply from 41.86.97.240: bytes=32 time=68ms TTL=51
Reply from 41.86.97.240: bytes=32 time=74ms TTL=51

Ping statistics for 41.86.97.240:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 83ms, Average = 72ms

-------------

Tracing route to vh-dns-01.vm.mweb.net [41.86.97.240]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms xxx.xxx.xxx.xxx <-------my firewall
2 1 ms 1 ms 2 ms xxx.xxx.xxx.xxx<--------my Gateway
3 9 ms 5 ms 3 ms 41.160.24.13
4 * * * Request timed out.
5 * * * Request timed out.
6 30 ms 27 ms 31 ms 41.164.0.243
7 30 ms 27 ms 27 ms 41.164.0.242
8 * 31 ms 29 ms mweb.cinx.net.za [196.223.22.32]
9 51 ms 33 ms 35 ms 197-84-7-2.cpt.mweb.co.za [197.84.7.2]
10 51 ms 35 ms 35 ms tengig0-7-0-1.vic-p-1.mweb.co.za [197.84.4.47]
11 63 ms 63 ms 54 ms vl-11.vic-hscore-1.mweb.co.za [197.80.5.237]
12 63 ms 54 ms 53 ms 197-80-96-54.jhb.mweb.co.za [197.80.96.54]
13 62 ms 53 ms 54 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
14 47 ms 33 ms 33 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
15 57 ms 32 ms 31 ms 148.75.28.196.netactive.net [196.28.75.148]
16 38 ms 32 ms 32 ms vh-dns-01.vm.mweb.net [41.86.97.240]

Trace complete.
 
@webtailor: Thanks!
Pinging the DNS server works. But the DNS queries timeout.

I can't do DNS lookups from the server, but also not from my laptop (I'm not sure if outside DNS queries will be handled by this DNS server.) Using "nslookup" on command line to test the DNS server.

I have temporarily switched my secondary DNS to Google DNS and this is working for now.
 
MWEB did send out notifications last week about issues affecting dns resolution.

We had notified them that their dns servers were caching records far and beyond what was considered acceptable.

After changing your dns servers make sure you run a ipconfig /flushdns on your VPS
 
I may not be on that mailing list. The last notice I received was 3 Oct i.r.t. "monthly maintenance". And their "network status" page also does not reflect any DNS issues.

The problem seems to be affecting ADSL users as well. The auto DNS of their ADSL Accounts is also not resolving. I just suggested to someone to change their DNS server ips on their connection and that solved the issue.

I did run ipconfig /flushdns ;)

BTW. I we have contacted them, and they have "escalated" our query (both of them) but I have not heard anything back so far. Guess it is not a "quick fix".
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X