Forum Home
PC World Chat
 
Thread ID: 121754 2011-11-11 04:17:00 No one has mentioned this either........ pctek (84) PC World Chat
Post ID Timestamp Content User
1243069 2011-11-13 03:06:00 When was the transfer done?
I was getting the old site, with the --- at the top of the page, at work which is a fibre connection with ubergroup.
Going there later so will check again.

It's all good at work now too. 		CYaBro (73)
1243070 2011-11-13 04:21:00 Ring who? Web Drive can't make fix Telstras DNS servers.

Have you tried using other ISPs servers instead of the default? Still not working here, or anyone else on Telstra cable.

I can just see whats going to happen -- telstra are going to say its webdrive and webdrive are going to say its telstra.

Funny (or not) both companies say they have people working over the weekends yet surprise surprise no one actually answers any emails or ticket requests.:rolleyes:

BUT at least with Webdrive you can actually talk to someone who can do something instead of getting shunted from person to person.

Its quite simple really, if Telsta say its web drives problem, then I'll simply transfer the domain name over to webdrive, then there wont be any its their fault crap.

As for the trying other DNS setting, YEP tried several and while all other pages loaded fine, mine still didn't. Thats whyI want to talk to someone who has the knowledge and can actually look to see where the problem is.
If you go into webdrives control panel and do a test to see if the DNS servers are directing correctly, it says Telsta is working. ( see attachment) So Webdrive say its working so who is incorrect) ??? 		wainuitech (129)
1243071 2011-11-13 04:41:00 Just found the problem (I think) Paradise's A record is pointing to the wrong IP

Holy moley -- Got someone on the phone @ telstra that sounds like they know what they are doing :D and can see the problem (we hope). 		wainuitech (129)
1243072 2011-11-13 04:50:00 When did you change your nameservers?

It looks like you previously had a 20 day expiry set on your SOA record, and TelstraClear's nameservers aren't obeying the 2-hour refresh interval. TelstraClear will be able to fix this if you call them, although you'll need to escalate it (possibly as far as their operations team) - the first level support people lack both the knowledge and access needed to resolve it.

What you need to ask for is for them to flush all records for your domain out of the caches for their recursive nameservers. 		Erayd (23)
1243073 2011-11-13 05:01:00 Just got off the phone, as the guy said, hes just changed the A record on paradise, as it was pointed to old IP -- The Telstra records change in a few minutes he said, but paradise ones can take up to 24-48 hours wainuitech (129)
1243074 2011-11-13 05:23:00 Just got off the phone, as the guy said, hes just changed the A record on paradise, as it was pointed to old IP -- The Telstra records change in a few minutes he said, but paradise ones can take up to 24-48 hoursI assume that TelstraClear realise they aren't your DNS provider any more? Your authoritative servers are currently set to ns1/ns2.nameserver.net.nz - those are WebDrive's servers; so updating your A records on TelstraClear servers wasn't the correct action (although it may remove the current symptom of the problem).

The problematic servers are rachel/kirsty.paradise.net.nz (203.96.152.4/12) - those servers think that *they* are the authoritative nameservers for commend.co.nz, so until that is rectified you may have ongoing issues with TelstraClear cable customers every time you change a DNS record of any kind.

What TelstraClear's servers think:

steve@neith ~ $ dig ns commend.co.nz @rachel.paradise.net.nz

; <<>> DiG 9.7.3 <<>> ns commend.co.nz @rachel.paradise.net.nz
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48303
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
; commend.co.nz. IN NS

;; ANSWER SECTION:
commend.co.nz. 1800 IN NS rachel.paradise.net.nz.
commend.co.nz. 1800 IN NS kirsty.paradise.net.nz.

;; ADDITIONAL SECTION:
kirsty.paradise.net.nz. 172800 IN A 203.96.152.12
rachel.paradise.net.nz. 172800 IN A 203.96.152.4

;; Query time: 11 msec
;; SERVER: 203.96.152.4#53(203.96.152.4)
;; WHEN: Sun Nov 13 18:26:18 2011
;; MSG SIZE rcvd: 118

Correct:

steve@neith ~ $ dig ns commend.co.nz @ns1.dns.net.nz

; <<>> DiG 9.7.3 <<>> ns commend.co.nz @ns1.dns.net.nz
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37879
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
; commend.co.nz. IN NS

;; AUTHORITY SECTION:
commend.co.nz. 86400 IN NS ns2.nameserver.net.nz.
commend.co.nz. 86400 IN NS ns1.nameserver.net.nz.

;; Query time: 24 msec
;; SERVER: 2001:dce:2000:2::130#53(2001:dce:2000:2::130)
;; WHEN: Sun Nov 13 18:26:20 2011
;; MSG SIZE rcvd: 82 		Erayd (23)
1243075 2011-11-13 06:15:00 I was told that Telsta are still the domain name holder, and they simply redirect any required settings to webdrives servers. The emails and domain name stay with Telstra.

One of the staff at webdrive said Telstra need to point the DNS to ns1/ns2.nameserver.net.nz , which they did, and it worked perfectly.

Every thing was working perfectly until Webdrive changed the site from a windows server to a linux server, and this was only because the form wasn't working in a windows server.
Now anyone on Telstra cable cant access anything. I had a look at the connections as shown before and according to webdrive all is working. (but it appears not)

BUT spot the difference :D The 168 was the old setting on the windows server.3367 Thats now been changed (or in the process). Previously if I tried to Ping the 165, it timed out, after speaking to telstra earlier today, I can now ping it and get a reply.

I've been with paradise for years, so thats where the actual domain is held. Why its not working on the cable is strange.

It all boils down to one thing -- Its not upto me to sort out the problems with a change over, I cant go into the settings and change things - its their systems someplace, all I can do is advise it not working. 		wainuitech (129)
1243076 2011-11-13 06:23:00 What no funky favicon? gary67 (56)
1243077 2011-11-13 06:28:00 :D Says who --- Maybe ;)

The one thats showing as previously mentioned is an older test version. The newer one has the typos corrected (thanks Pctek) and the layout slightly different.

It's still work in progress -- and a LOT of work at that, considering I'm no web designer, and threw that together in a few hours.

You want to see a great site -- look up CYaBro's :thumbs: 		wainuitech (129)
1243078 2011-11-13 07:02:00 I was told that Telsta are still the domain name holder...and domain name stay with TelstraYep, but they're not your DNS provider - they're just the registrar.


...and they simply redirect any required settings to webdrives servers.That's what they should be doing, but rachel/kirsty seem to be reporting otherwise. I'd recommend you change another DNS record on the WebDrive end (or add one), and if it doesn't automatically show up on the TelstraClear servers within a couple of days, you'll need to call TelstraClear and get them to correct the settings on their nameservers.


The emails...stay with Telstra.Are you aware that you only have one MX record? This means that any mail sent while that server is down will be either delayed or bounced, and if the server is down for too long everything would bounce. Best practice is to have at least two mailservers, ideally more.


One of the staff at webdrive said Telstra need to point the DNS to ns1/ns2.nameserver.net.nz , which they did, and it worked perfectly.It appears that Telstra have done this, but they've forgotten to also update the config on their nameservers - which they very likely need to do.


Every thing was working perfectly until Webdrive changed the site from a windows server to a linux server, and this was only because the form wasn't working in a windows server.It wasn't working perfectly, it just *looked* like it was working perfectly because the settings were the same.


Now anyone on Telstra cable cant access anything. I had a look at the connections as shown before and according to webdrive all is working. (but it appears not)WebDrive's end (DNS-wise) is fine, Telstra is the one at fault here.


Previously if I tried to Ping the 165, it timed out, after speaking to telstra earlier today, I can now ping it and get a reply.If you were pinging the IP directly rather than pinging the hostname, then that wasn't anything to do with Telstra. If you were pinging the hostname, then it was a symptom of your DNS issues.


I've been with paradise for years, so thats where the actual domain is held. Why its not working on the cable is strange.It's not working on the cable because rachel and kirsty aren't configured properly.


It all boils down to one thing -- Its not upto me to sort out the problems with a change over, I cant go into the settings and change things - its their systems someplace, all I can do is advise it not working.Very true!

Out of interest, how much is TelstraClear charging you to be the registrar for commend.co.nz? Last time I looked, their prices were an absolute rip-off. 		Erayd (23)
1 2 3 4 5 6 7