Intermittent in resolving subdomain ncd.ism.net.my from 26/9/14 - 3/10/14 via Go

[ari...@gmail.com]

On 26/9/2014, we received several complaints from users within Malaysia unable to access one of our subdomain which is ncd.ism.net.my. Upon investigation, we managed to find out that Google OpenDNS (8.8.8.8) unable to resolve our subdomain at ncd.ism.net.my. The connection is intermittent as sometimes it works, and sometimes not. Upon running nslookup to resolve our nameserver, google fail to resolve our subdomain. However, all other subdomain and TLD have no issues at all. 

Issues persists until 3/10/2014 and upon tests, Google DNS was able to resolve our domain without any problem. 

May i ask does Google DNS in Malaysia have any issues during that time in resolving our domain (ncd.ism.net.my) as we have test with all Malaysian's default ISP and found no issues at all, and we have test using several public DNS such as OpenDNS, Level3 Comm DNS and found no issues in resolving our nameserver. 

I hoped i could receive some feedback prior to this as we need to prepare report prior to this incident.  

Further technical details of the issue are below and refer attachment for nslookup tests done by us. 

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

Thanks & Best Regards,

- Mohd Arief Bin Mohd Ramli - 

[ari333f]

Any update on this issue? I have just tested using GoogleDNS right now (9/11/2014 @ 10:05pm GMT +8) and still unable to resolve ncd.ism.net.my. No issues at all using other DNS. 

Refer below:

C:\Users\Lemon>nslookup ncd.ism.net.my

Server:  google-public-dns-a.google.com

Address:  8.8.8.8

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\Lemon>ping ncd.ism.net.my

Ping request could not find host ncd.ism.net.my. Please check the name and try a

gain.

C:\Users\Lemon>ping www.ism.net.my

Pinging www.wip.ism.net.my [203.115.229.12] with 32 bytes of data:

Reply from 203.115.229.12: bytes=32 time=33ms TTL=251

Reply from 203.115.229.12: bytes=32 time=33ms TTL=251

Reply from 203.115.229.12: bytes=32 time=32ms TTL=251

Reply from 203.115.229.12: bytes=32 time=32ms TTL=251

Ping statistics for 203.115.229.12:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 32ms, Maximum = 33ms, Average = 32ms

C:\Users\Lemon>

[Lemon Tree]

Dear Support,

Recently we have encountered the same issue resolving our nameserver with only Google DNS (8.8.8.8).

We have no issues resolving our nameserver using all other Public DNS. Kindly look into this matter. 

C:\Users\Lemon>ping ncd.ism.net.my

Ping request could not find host ncd.ism.net.my. Please check the name and try a

gain.

C:\Users\Lemon>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.

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

Best Regards,

Mohd Arief Ramli.

[Grant Ridder]

DNSsec error
http://dnsviz.net/d/ncd.ism.net.my/dnssec/

Sent from my iPhone

> On Jan 30, 2015, at 5:07 PM, Lemon Tree <ari...@gmail.com> wrote:
>
> ncd.ism.net.my

[Lemon Tree]

Ok thanks. We will look into it. However, it is quite weird why other Public DNS able to resolve our nameserver though. 

[ari333f]

Thanks Grant.

Error from dnnsec as per following. However, how come other DNS provider able to resolve our nameserver?

• net.my. to ism.net.my.: The server(s) were not responsive to queries over UDP. (121.123.140.236)

--

Thanks & Best Regards,

Mohd Arief Ramli