Level 2: Rookie

traceroute to telstra dns server loops

Answered

I have been having dns issues with no response from either dns servers. Logging into my Telstra gateway and doing a traceroute to the ip addresses both loop

e.g.

traceroute to 61.9.194.49 (61.9.194.49), 64 hops max
  3   *  *  *  
  4   61.9.194.49  9.166ms  15.927ms  7.788ms  
  5   172.18.239.225  12.280ms  10.206ms  9.761ms  
  6   61.9.194.49  15.405ms  10.286ms  8.133ms  
  7   172.18.239.225  11.548ms  10.480ms  10.086ms  
  8   61.9.194.49  14.603ms  9.184ms  9.620ms  

...

 64 61.9.194.49  13.922ms  11.655ms  11.448ms 

The other

traceroute to 61.9.195.193 (61.9.195.193), 64 hops max

***
  3   58.160.249.2  9.393ms  9.616ms  10.029ms  
  4   172.18.80.134  10.087ms  14.028ms  10.099ms  
  5   61.9.195.193  9.623ms  10.931ms  9.331ms  
  6   172.18.239.97  10.242ms  10.434ms  9.244ms  
  7   61.9.195.193  9.455ms  10.568ms  9.254ms  
  8   172.18.239.97  17.756ms  10.673ms  9.783ms  

...

64 172.18.239.97  15.341ms  11.022ms  12.045ms 

 

When DNS eventually came back the traceroute still loops %-(

61.9.195.193 => dns-cust.ken.bigpond.net.au.

61.9.194.49  => dns-cust.cht.bigpond.net.au

172.*  is "intranet So I assume it is Telstra internal.

How do I report this to Telstra as support tells me I have to go through "Platinum" support and pay for the privilege.

 

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Level 23: Superhero
Level 23: Superhero
Accepted Solution

Re: traceroute to telstra dns server loops

Hey, can you provide some more context into which servers you are trying to reach. Also have you tried changing the DNS servers on your computer to Google's (8.8.8.8 and 8.8.4.4) to see if that makes any difference.
For Official Support Chat Now, try the Online Troubleshooter, check for Outages or Raise a Complaint.

Full Disclosure as part of Telstras Social Media Code.
  • I work for Telstra in the following products.
  • Telstra Platinum, Telstra Business Services, Telstra Smart Home, Velocity, Locator and NBN faults.
  • I'm not here in an official capacity, I just like fixing things and respond in my own time when I can.
  • Include "@343GuiltySpark" in your reply to get my attention if you're after me specifically.
  • My opinions are my own and not that of Telstra's, just so we're all on the same page.

View solution in original post

Was this helpful?

  • Yes it was, thank you
  • No, I still need help
9 REPLIES 9
Level 23: Superhero
Level 23: Superhero
Accepted Solution

Re: traceroute to telstra dns server loops

Hey, can you provide some more context into which servers you are trying to reach. Also have you tried changing the DNS servers on your computer to Google's (8.8.8.8 and 8.8.4.4) to see if that makes any difference.
For Official Support Chat Now, try the Online Troubleshooter, check for Outages or Raise a Complaint.

Full Disclosure as part of Telstras Social Media Code.
  • I work for Telstra in the following products.
  • Telstra Platinum, Telstra Business Services, Telstra Smart Home, Velocity, Locator and NBN faults.
  • I'm not here in an official capacity, I just like fixing things and respond in my own time when I can.
  • Include "@343GuiltySpark" in your reply to get my attention if you're after me specifically.
  • My opinions are my own and not that of Telstra's, just so we're all on the same page.

View solution in original post

Level 2: Rookie

Re: traceroute to telstra dns server loops

I can dig 8.8.8.8. The Telstra Broadband Gateway provided  (Netgear C6300BD -  Gateway MAX) does not allow me to configure dns servers, and I am using it as my DHCP Server. I used to have a dd-wrt wifi router (it does not have 5G) but turned it off when I went to Telstra.

 

Perhaps I will resurrect it - but I feel that Telstra is "coping out". I imagine that because when NBN takes over my area (March 2019 !) they will wear the problem.

 

Thanks high heeled boy %-)

Level 2: Rookie

Re: traceroute to telstra dns server loops

I did not accept your answer as solution - it was justa tick I didn't see.
When the dns servers are unreachable no dns query works.
I have been having another intermittent issue where the the wan connection is lost and so between these issues its often hard to know which path to trouble shoot.
p.s.
Sorry but I read GuiltySpark as Low Spark. An album by Traffic
- The Low Spark Of High Heeled Boys.
Level 19: Deputy Director

Re: traceroute to telstra dns server loops

Perhaps if you login to Telstra router and post the connection log that shows details of the connection ie errors, type of errors etc.
Level 23: Superhero
Level 23: Superhero

Re: traceroute to telstra dns server loops

Are you on cable internet? You're WAN going down sounds like you may have a drop fault.
For Official Support Chat Now, try the Online Troubleshooter, check for Outages or Raise a Complaint.

Full Disclosure as part of Telstras Social Media Code.
  • I work for Telstra in the following products.
  • Telstra Platinum, Telstra Business Services, Telstra Smart Home, Velocity, Locator and NBN faults.
  • I'm not here in an official capacity, I just like fixing things and respond in my own time when I can.
  • Include "@343GuiltySpark" in your reply to get my attention if you're after me specifically.
  • My opinions are my own and not that of Telstra's, just so we're all on the same page.
Level 21: Augmented

Re: traceroute to telstra dns server loops

OK, doing it from my modem, it does the same and I would think there is issue with traceroute implementation in the modem... Trying to do traceroute from my Linux box produces timeouts which is not surprising... Most router admins disable ICMP ping on them due to security risks so traceroute does not work...

However, the servers respond without any issue (I am doing this from Telstra NBN FTTN):

~$ dig @61.9.194.49 www.mit.edu

; <<>> DiG 9.10.3-P4-Ubuntu <<>> @61.9.194.49 www.mit.edu
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54264
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.mit.edu.                   IN      A

;; ANSWER SECTION:
www.mit.edu.            674     IN      CNAME   www.mit.edu.edgekey.net.
www.mit.edu.edgekey.net. 60     IN      CNAME   e9566.dscb.akamaiedge.net.
e9566.dscb.akamaiedge.net. 20   IN      A       104.116.121.51

;; Query time: 174 msec
;; SERVER: 61.9.194.49#53(61.9.194.49)
;; WHEN: Wed Feb 21 20:23:57 DST 2018
;; MSG SIZE  rcvd: 129

~$ dig @61.9.195.193 www.mit.edu

; <<>> DiG 9.10.3-P4-Ubuntu <<>> @61.9.195.193 www.mit.edu
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5103
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.mit.edu.                   IN      A

;; ANSWER SECTION:
www.mit.edu.            1800    IN      CNAME   www.mit.edu.edgekey.net.
www.mit.edu.edgekey.net. 40     IN      CNAME   e9566.dscb.akamaiedge.net.
e9566.dscb.akamaiedge.net. 20   IN      A       118.215.113.86

;; Query time: 32 msec
;; SERVER: 61.9.195.193#53(61.9.195.193)
;; WHEN: Wed Feb 21 20:24:46 DST 2018
;; MSG SIZE  rcvd: 129
DISCLAIMER: I do not work for Telstra or any other ISP. I never did. I have wealth of practical knowledge in Computer Security and Forensic Computing. I have been in the field since 1985.

Likes (formerly Kudos) and solutions are appreciated!!!
The comments expressed by me reflect my user experience and personal opinion.
Level 2: Rookie

Re: traceroute to telstra dns server loops

I did my traceroute from a linux machine behind the gateway. My windows machine provided timeouts.
 
As I am typing this the gateway has lost wan connection - but there is nothing in the event log. I have put those errors down the bottom. It just suddenly dropped around 07:35 AEST.
 
 The earlier errors are like these (Timestamps are in UTC so add 11 hours).
 
1/
 
Wed Feb 21 11:55:31 2018       Critical (3)      Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=18:e7:28:1d:9b:69;CM-QOS=1.1;CM-VER=3.0;
 
and
 
2/
 
Fri Feb 16 11:25:13 2018       Critical (3)      Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=18:e7:28:1d:9b:7d;CM-QOS=1.1;CM-VER=3.0;
 
Times (UTC) .
 
Wed Feb 21 11:55:31 2018         
 Tue Feb 20 20:56:01 2018         
 Tue Feb 20 20:45:50 2018         
 Tue Feb 20 20:31:04 2018         
 Tue Feb 20 20:06:04 2018         
 Tue Feb 20 20:00:53 2018         
 Tue Feb 20 19:51:02 2018         
 Tue Feb 20 19:40:52 2018         
 Fri Feb 16 11:25:13 2018         
 Fri Feb 16 10:53:04 2018         
 Thu Feb 15 22:57:08 2018         
 Thu Feb 15 10:23:35 2018         
 Thu Feb 15 08:23:36 2018         
 Wed Feb 14 03:50:40 2018         
 Wed Feb 14 03:49:57 2018         
 Wed Feb 14 03:49:08 2018         
 Wed Feb 14 03:48:48 2018         
 Tue Feb 13 21:20:34 2018         
 Tue Feb 13 16:33:38 2018         
 Fri Feb 02 08:30:11 2018         
 Fri Feb 16 11:25:13 2018         
 Fri Feb 16 10:53:04 2018         
 Thu Feb 15 22:57:08 2018         
 Thu Feb 15 10:23:35 2018         
 Thu Feb 15 08:23:36 2018         
 Wed Feb 14 03:50:40 2018         
 Wed Feb 14 03:49:57 2018         
 Wed Feb 14 03:49:08 2018         
 Wed Feb 14 03:48:48 2018         
 Tue Feb 13 21:20:34 2018         
 Tue Feb 13 16:33:38 2018         
 Fri Feb 02 08:30:11 2018         
 Fri Feb 02 08:27:06 2018         
 Fri Feb 02 08:21:52 2018         
 Fri Feb 02 08:12:20 2018         
 Fri Feb 02 08:05:23 2018         
 Fri Feb 02 07:00:21 2018         
 Fri Feb 02 06:41:41 2018         
 Fri Feb 02 06:41:21 2018

 

This morning when it dropped errors were (after reboot in reverse time order)

Time     Priority     Description

 Time Not Established      Notice (6)      Honoring MDD; IP provisioning mode = IPv4  
 Time Not Established      Critical (3)      SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Critical (3)      No UCDs Received - Timeout;;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
Time Not Established      Warning (5)      Lost MDD Timeout;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Critical (3)      DHCP FAILED - Discover sent, no offer received;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=18:e7:28:1d:9b:69;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Notice (6)      Honoring MDD; IP provisioning mode = IPv4  
 Time Not Established      Critical (3)      SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Critical (3)      No UCDs Received - Timeout;;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Warning (5)      Lost MDD Timeout;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Critical (3)      No UCDs Received - Timeout;;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Warning (5)      Lost MDD Timeout;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Critical (3)      DHCP FAILED - Discover sent, no offer received;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=18:e7:28:1d:9b:69;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Notice (6)      Honoring MDD; IP provisioning mode = IPv4  
 Time Not Established      Critical (3)      SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Critical (3)      No UCDs Received - Timeout;;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Warning (5)      Lost MDD Timeout;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Critical (3)      DHCP FAILED - Discover sent, no offer received;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=18:e7:28:1d:9b:7d;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Notice (6)      Honoring MDD; IP provisioning mode = IPv4  
 Time Not Established      Critical (3)      SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Critical (3)      No UCDs Received - Timeout;;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Warning (5)      Lost MDD Timeout;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Critical (3)      No UCDs Received - Timeout;;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Warning (5)      Lost MDD Timeout;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;  
 Time Not Established      Critical (3)      DHCP FAILED - Discover sent, no offer received;CM-MAC=10:da:43:f3:f9:89;CMTS-MAC=18:e7:28:1d:9b:69;CM-QOS=1.0;CM-VER=3.0;  
 --------------------------------------------------

I am on Telstra "HFC" which I expect I will stay on when NBN moves in.

Is it possible to diagnose the MDD,FEC,Sync Timing as being to physical issues at my end of the connection ?

I logged a call and they arranged a technician callout. When it came back I cancelled the call, but would like to know for next time.

Telstra needs to sort out its level of support. The call desk is basic - and then for anything else you have to accept Platinum charge for service. I know my issue is NOT my fault but there is no way for me to get it looked at by anyone with any knowledge.

 

Cheers.

Level 2: Rookie

Re: traceroute to telstra dns server loops

Our region suffered from an outage today.

In regard to this issue I have decided that trying to traceroute or ping the Telstra DNS servers is not a useful diagnosis to attempt.

If you can ping the telstra Gateway router assume your connection is alive.

dig/nslookup using telstra servers and if that fails dig/nslookup google (8.8.8.8 or 8.8.4.4).

 

Maybe someday someone in Telstra will know about this looping traceroute and fix it (or ignore it).

I will tick this as solved

 

Level 21: Augmented

Re: traceroute to telstra dns server loops

AS I said, using traceroute or ping is not good idea due to more and more SysAdmins disabling ICMP for security reasons. Layer four ping (lft) or advanced tools like nmap should be used for more advanced troubleshooting, but simple "dig @x.x.x.x y.y.y.y" should be good enough for testing.
As for the loop - when doing my "home work" before posting last night, I found CISCO whitepaper describing exactly the same issue in a cases of not 100% correctly configured (but fully functional) redundant routes...
DISCLAIMER: I do not work for Telstra or any other ISP. I never did. I have wealth of practical knowledge in Computer Security and Forensic Computing. I have been in the field since 1985.

Likes (formerly Kudos) and solutions are appreciated!!!
The comments expressed by me reflect my user experience and personal opinion.

Set it & forget it

With direct debit there’s no need to give paying your bill another thought.

Avoid queuing up and never worry about late fees again.

Setup direct debit