DNS resolution issues with www.mycloudnas.com

[icekool79]

Hi

I've set up my Qnap 419 to use the http://www.mycloudnas.com DDNS and most of the time the server resolves but quite often the DNS resolution is lost.

I've done some tests and pasted the results below the below lookups are done within a few minutes of each other. The first 4 show the DNS correctly resolving, and then immediately after the resolution is lost. This is making the DDNS setup unusable as it stops working intermittently.

Is anyone else having this issue?
I'd prefer to use the mycloudnas.com address, but is there anyway to fix this?
The only thing I can think of is that the Domain Registry that manages the http://www.mycloudnas.com entry needs to repush the setup???

Thanks


1) WORKING DNS

C:\Users\Peter>nslookup http://www.mycloudnas.com 203.0.178.191
Server: dns.iinet.net.au
Address: 203.0.178.191

Non-authoritative answer:
Name: http://www.mycloudnas.com
Address: 211.78.89.233


C:\Users\Peter>nslookup http://www.mycloudnas.com 203.215.29.191
Server: dns2.iinet.net.au
Address: 203.215.29.191

Non-authoritative answer:
Name: http://www.mycloudnas.com
Address: 211.78.89.233


C:\Users\Peter>nslookup http://www.mycloudnas.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: http://www.mycloudnas.com
Address: 211.78.89.233


C:\Users\Peter>nslookup http://www.mycloudnas.com 8.8.4.4
Server: google-public-dns-b.google.com
Address: 8.8.4.4

Non-authoritative answer:
Name: http://www.mycloudnas.com
Address: 211.78.89.233



2) FAILING DNS


C:\Users\Peter>nslookup http://www.mycloudnas.com 203.0.178.191
Server: dns.iinet.net.au
Address: 203.0.178.191

*** dns.iinet.net.au can't find http://www.mycloudnas.com: Server failed

C:\Users\Peter>nslookup http://www.mycloudnas.com 203.215.29.191
Server: dns2.iinet.net.au
Address: 203.215.29.191

*** dns2.iinet.net.au can't find http://www.mycloudnas.com: Server failed

C:\Users\Peter>nslookup http://www.mycloudnas.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

*** google-public-dns-a.google.com can't find http://www.mycloudnas.com: Server failed

C:\Users\Peter>nslookup http://www.mycloudnas.com 8.8.4.4
Server: google-public-dns-b.google.com
Address: 8.8.4.4

*** google-public-dns-b.google.com can't find http://www.mycloudnas.com: Server failed

[schumaku]

Partially correct... I'm still convinced the MyCloudNAS.com, MyQNAPNAS.com, or QCloudNAS.com basic DNS domain set-up is broken - and this can and will lead to problems resolving any of these domains. In my understanding of DNS (which is certainly not that poor...), it's kind of a wonder http://www.mycloudnas.com (or any other related doamins like [MyCloudNASName].mycloudnas.com, [MyCloudNASName].MyQNAPNAS.com, or [MyCloudNASName].QCloudNAS.com ) can be resolved to an A record

When it comes to your testing: I doubt neither DNS nor the related tools like nslookup, dig, or simiar can resolve an IP (A record) from an URL - to be on a food base, just FQDN or hostnames cna be resolved.

But then: Yes, I can confirm

1. The Google public DNS have probelsm to resolve http://www.mycloudnas.com (or similar) in a reliable way.
2. Some DNS services (private or ISP) are not able to resolve any address from the QNAP cloud domains.
3. The DNS for all three doamins above is abdly broken:

Doing some "any" queries unveils this - first a complete one, here http://www.qnap.com:

> set type=any
> http://www.qnap.com
Server: localhost
Address: 127.0.0.1

Non-authoritative answer:
http://www.qnap.com canonical name = http://www.qnap.com.edgesuite.net

Authoritative answers can be found from:
qnap.com nameserver = tpe-dns1.dwins.com.tw
qnap.com nameserver = tpe-dns4.dwins.com.tw
tpe-dns1.dwins.com.tw internet address = 211.78.80.3
tpe-dns4.dwins.com.tw internet address = 211.78.81.140



Interestingly, the A record (the address) can be resolved now from here - however, not the IP addresses of the name servers.

In my opinion:

1. The SOA record is missing for mycloudnas.com:

> set type=soa
> mycloudnas.com
Server: localhost
Address: 127.0.0.1

*** localhost can't find mycloudnas.com: Non-existent host/domain
> MyQNAPNAS.com
Server: localhost
Address: 127.0.0.1

*** localhost can't find MyQNAPNAS.com: Non-existent host/domain
> QCloudNAS.com
Server: localhost
Address: 127.0.0.1

*** localhost can't find QCloudNAS.com: Non-existent host/domain

2. The NS records for the domains cant be found:

> QCloudNAS.com
Server: localhost
Address: 127.0.0.1

*** localhost can't find QCloudNAS.com: Non-existent host/domain
> mycloudnas.com
Server: localhost
Address: 127.0.0.1

*** localhost can't find mycloudnas.com: Non-existent host/domain
> MyQNAPNAS.com
Server: localhost
Address: 127.0.0.1

*** localhost can't find MyQNAPNAS.com: Non-existent host/domain
> QCloudNAS.com
Server: localhost
Address: 127.0.0.1

*** localhost can't find QCloudNAS.com: Non-existent host/domain

3. Interetingly, sometimes two name ervers are listed when doing the ALL query - but these dont resolve to an IP here:

> set type=ANY
> mycloudnas.com
Server: localhost
Address: 127.0.0.1

Non-authoritative answer:
mycloudnas.com internet address = 211.78.89.233
mycloudnas.com nameserver = ns1.mycloudnas.com
mycloudnas.com nameserver = ns2.mycloudnas.com

Authoritative answers can be found from:
mycloudnas.com nameserver = ns2.mycloudnas.com
mycloudnas.com nameserver = ns1.mycloudnas.com
> MyQNAPNAS.com
Server: localhost
Address: 127.0.0.1

Non-authoritative answer:
MyQNAPNAS.com internet address = 211.78.89.233
MyQNAPNAS.com nameserver = ns2.MyQNAPNAS.com
MyQNAPNAS.com nameserver = ns1.MyQNAPNAS.com

Authoritative answers can be found from:
MyQNAPNAS.com nameserver = ns2.MyQNAPNAS.com
MyQNAPNAS.com nameserver = ns1.MyQNAPNAS.com
> QCloudNAS.com
Server: localhost
Address: 127.0.0.1

Non-authoritative answer:
QCloudNAS.com internet address = 211.78.89.233
QCloudNAS.com nameserver = ns1.QCloudNAS.com
QCloudNAS.com nameserver = ns2.QCloudNAS.com

Authoritative answers can be found from:
QCloudNAS.com nameserver = ns2.QCloudNAS.com
QCloudNAS.com nameserver = ns1.QCloudNAS.com

4. None of the name servers listed cna be resolved:

> set type=a
> ns1.mycloudnas.com
Server: localhost
Address: 127.0.0.1

*** localhost can't find ns1.mycloudnas.com: Non-existent host/domain
> ns2.mycloudnas.com
Server: localhost
Address: 127.0.0.1

*** localhost can't find ns2.mycloudnas.com: Non-existent host/domain
> ns1.QCloudNAS.com
Server: localhost
Address: 127.0.0.1

*** localhost can't find ns1.QCloudNAS.com: Non-existent host/domain
> ns2.QCloudNAS.com
Server: localhost
Address: 127.0.0.1

*** localhost can't find ns2.QCloudNAS.com: Non-existent host/domain
> ns2.QCloudNAS.com
Server: localhost
Address: 127.0.0.1

*** localhost can't find ns2.QCloudNAS.com: Non-existent host/domain
> ns1.QCloudNAS.com
Server: localhost
Address: 127.0.0.1

*** localhost can't find ns1.QCloudNAS.com: Non-existent host/domain
>

So how shsould "any" DNS client out there be able to resolve any of these domains hosts, when not even the defined name servers can't be resolved?

[icekool79]

@schumaku Cheers thanks for that really helpful. Good to know its not just me that has this problem. Hopefully someone in QNAP can organise a fix cause I'd hate for MyCloudNas to be a not very useful DDNS.

[nhanes]

i have the same problem.
Would QNAP fix it?

[f0rky]

having the same issue as mentioned here... the TTL on the records are really low and the qnap dns servers don't seem to respond reliably

[icekool79]

I still have this issue at the moment.

Fingers crossed if enough of us have this issue qnap might do something about it.

[schumaku]

the TTL on the records are really low...

Any alternate suggestions for a DDNS system?

and the qnap dns servers don't seem to respond reliably

Proof? We know some content filter systems contain the QNAP' and dother providers DDNS service names - so depending on the service setings in corporat infrastructure, a look-up can be completely denied.

Fingers crossed if enough of us have this issue qnap might do something about it.

the ns1 and ns2 for the dodmains are deployed now. Odd everyhting is pointing to just a single IP - which can certainly lead to service interruption or delays in resolving.

While the DNS configuration for mycloudnas.com domain looks much better now (ns1 and ns2 are resolving and exist) the NS records required by all host lookups for QCloudNAS.com or MyQNAPNAS.com still don't exist.