Unable to resolve subdomain ncd.ism.net.my
ari333f
We received several complaints from users within Malaysia unable to access one of our subdomain which is ncd.ism.net.my since last week friday (31/10/2014). Even now i have tested using Google Public DNS and unable to resolve ncd.ism.net.my whereas i am able to resolve our nameserver using OpenDNS, and our default ISP (Telekom Malaysia) DNS. Google DNS have no issues at all resolving our Top Level Domain (TLD) at www.ism.net.my and any other subdomain such as members.ism.net.my. We have raised this issue last time (refer to Issue 775 ) as you have mentioned you do not have any logs prior to this incident. Kindly refer to the attachment of this Issue for the nslookup result using different DNS provider. You have mentioned that it might be an issue for those behind F5 appliances. Hoped you could look into this matters as we have several users complaining on this.
We have raised another Issue Ticket 794 prior to this incident. Further technical details of the issue are below:
Google DNS at 11:08 AM 3rd November 2014
C:\Users\ism.admin>ipconfig /flushdns
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
C:\Users\ism.admin>nslookup ncd.ism.net.my
Server: google-public-dns-a.google.com
Address: 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
*** google-public-dns-a.google.com can't find ncd.ism.net.my: Non-existent domain
C:\Users\ism.admin>ping ncd.ism.net.my
Ping request could not find host ncd.ism.net.my. Please check the name and try again.
Telekom DNS @ 202.188.0.133 at 11:13 AM 3rd November 2014
C:\Users\ism.admin>ipconfig /flushdns
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
C:\Users\ism.admin>nslookup ncd.ism.net.my
Server: cns3.tm.net.my
Address: 202.188.0.133
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
DNS request timed out.
timeout was 2 seconds.
Name: ncd.wip.ism.net.my
Address: 203.115.229.20
Aliases: ncd.ism.net.my
C:\Users\ism.admin>ping ncd.ism.net.my
Pinging ncd.wip.ism.net.my [203.115.229.20] with 32 bytes of data:
Reply from 203.115.229.20: bytes=32 time=33ms TTL=254
Reply from 203.115.229.20: bytes=32 time=32ms TTL=254
Reply from 203.115.229.20: bytes=32 time=110ms TTL=254
Reply from 203.115.229.20: bytes=32 time=118ms TTL=254
Ping statistics for 203.115.229.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 118ms, Average = 73ms
OpenDNS at 11:16 AM 3rd November 2014
C:\Users\ism.admin>ipconfig /flushdns
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
C:\Users\ism.admin>nslookup ncd.ism.net.my
Server: resolver1.opendns.com
Address: 208.67.222.222
Non-authoritative answer:
DNS request timed out.
timeout was 2 seconds.
Name: ncd.wip.ism.net.my
Address: 203.115.229.20
Aliases: ncd.ism.net.my
C:\Users\ism.admin>ping ncd.ism.net.my
Pinging ncd.wip.ism.net.my [203.115.229.20] with 32 bytes of data:
Reply from 203.115.229.20: bytes=32 time=36ms TTL=254
Reply from 203.115.229.20: bytes=32 time=424ms TTL=254
Reply from 203.115.229.20: bytes=32 time=38ms TTL=254
Reply from 203.115.229.20: bytes=32 time=50ms TTL=254
Ping statistics for 203.115.229.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 424ms, Average = 137ms