MTN website woes: response

Yet the site still doesn't redirect properly if you don't punch in the www.

Seriously, this take two minutes to fix.
 
Re-engineer is quite a big word to be used here and since they did use the word, they acknowledged that they are quite terrible at engineering things.
 
kwaggawerner said:
I wouldn't call it "teething problems"... That's what beta testing is for.
Click to expand...

Ja. If even one second was spent on real user beta testing, they would have seen the problems. You should get your shift correct before releasing. I feel this "teething" problem really means "we f-ed up but can't admit it" which actually means "MD4E hacked us"

DrJohnZoidberg said:
Yet the site still doesn't redirect properly if you don't punch in the www.
Seriously, this take two minutes to fix.
Click to expand...

My prior knowledge of MTN tells me that the person to modify the zone and the agency for the development of the site are miles apart. Talking to each other would be unheard of. Nobody knows who the domain admin is.

Fulcrum29 said:
Re-engineer is quite a big word to be used here and since they did use the word, they acknowledged that they are quite terrible at engineering things.
Click to expand...

I am coming to loathe that word more and more. To me, it is like "learner" for "pupil" and is nothing more than an expensive way of saying "updated".
 
It's obvious that absolutely no quality assurance testing was done on this site at all before it was released to live. And from what I can see, no integration testing, and probably no unit testing either.

Furthermore, they are using .NET for their website, which is great, but why on earth are they still using WebForms instead of MVC?

Real amateur stuff.
 
Most annoying is my inability to get itemised billing information. You know, that service they have the gall to charge R19/month for.... yeah, that thing. :mad:
 
DrJohnZoidberg said:
Yet the site still doesn't redirect properly if you don't punch in the www.

Seriously, this take two minutes to fix.
Click to expand...

It does but the comment seems to indicate, it aint just a redirect problem. Its more like WTF now problem.:cry:
 
You're the two guys who probably set it up for them then, since it aint a DNS problem:

$ nslookup mtn.co.za
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: mtn.co.za
Address: 196.11.240.215

$ nslookup www.mtn.co.za
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: www.mtn.co.za
Address: 196.11.240.215
 
GreGorGy said:
You're the two guys who probably set it up for them then, since it aint a DNS problem:

$ nslookup mtn.co.za
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: mtn.co.za
Address: 196.11.240.215

$ nslookup www.mtn.co.za
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: www.mtn.co.za
Address: 196.11.240.215
Click to expand...

Lol. That just means it's even easier to fix :D
 
GreGorGy said:
You're the two guys who probably set it up for them then, since it aint a DNS problem:

$ nslookup mtn.co.za
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: mtn.co.za
Address: 196.11.240.215

$ nslookup www.mtn.co.za
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: www.mtn.co.za
Address: 196.11.240.215
Click to expand...



thats exactly the problem... you don't route subdomains to the same ip even if www is usually sent there. you route subdomains to a load-balancer / routing script in a different datacenter and from there to your destination of choice. what happens if mtn.co.za goes down in your case? does mail. www. ftp. mahalaphones. also go down? why yes.. it does... whereas if you resolve your subdomains to a seperate IP.. not only don't you have to wait for global DNS cache updates every time you make a change... but you can also route subdomains on the fly... but wait.. theres more... because then it enables you route to a landing/error/sorry we are offline page whilst the datacenter fetishists goes and figures out why mtn.co.za blew up...
 
stricken said:
thats exactly the problem... you don't route subdomains to the same ip even if www is usually sent there. you route subdomains to a load-balancer / routing script in a different datacenter and from there to your destination of choice. what happens if mtn.co.za goes down in your case? does mail. www. ftp. mahalaphones. also go down? why yes.. it does... whereas if you resolve your subdomains to a seperate IP.. not only don't you have to wait for global DNS cache updates every time you make a change... but you can also route subdomains on the fly... but wait.. theres more... because then it enables you route to a landing/error/sorry we are offline page whilst the datacenter fetishists goes and figures out why mtn.co.za blew up...
Click to expand...

That's nice. It is NOT the problem though. Their (MTN) problem is that the 302 Moved redirect on http://mtn.co.za/* goes to www.mtn.co.za instead of http://www.mtn.co.za/

What you are saying has value - it is just not the problem with their mtn.co.za web call going haywire.
 
Think they watching this thread,redirect problem seems fixed
 
DrJohnZoidberg said:
Yet the site still doesn't redirect properly if you don't punch in the www.

Seriously, this take two minutes to fix.
Click to expand...

the number of South African web hosters whose DNS systems don't automatically create a CNAME for www is appalling.

But then most SA web hosters don't use cpanel / whm or plesk control panels.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X