# Sub domaine syncloud.it can't be resolve

**URL:** <https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397>\
**Category:** Syncloud.it\
**Created:** [20 November 2023 17:35 UTC](https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397 "2023-11-20T17:35:00Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![pirboazo](https://avatars.discourse-cdn.com/v4/letter/p/a183cd/32.png) [@pirboazo](https://syncloud.discourse.group/u/pirboazo)\
**Post date:** [20 November 2023 17:35 UTC](https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397/1 "2023-11-20T17:35:00Z")

</div>

Hi support

I activate my new device with the name m\*\*\*y.syncloud.it.

```auto
@sony-vaio:~$ nslookup m***y.syncloud.it
Server: 192.168.1.1
Address:	192.168.1.1#53

Non-authoritative answer:
***Can't find m*** y.syncloud.it: No answer

```

I verify than my dns resolution work correctly.

```auto
sony-vaio:~$ nslookup syncloud.it
Server: 192.168.1.1
Address:	192.168.1.1#53

Non-authoritative answer:
Name:	syncloud.it
Address: 54.70.47.240
Name:	syncloud.it
Address: 2600:1f14:a96:4d03:ef04:d13c:7344:26bf

```

my syncloud site work also.

```auto
sony-vaio:~$ nslookup g***n.me
Server: 192.168.1.1
Address:	192.168.1.1#53

Non-authoritative answer:
Name:	g***n.me
Address: 62. ***.***.37

```

Regard  
Pierre

---

<div class="post-metadata">

**Author:** ![pirboazo](https://avatars.discourse-cdn.com/v4/letter/p/a183cd/32.png) [@pirboazo](https://syncloud.discourse.group/u/pirboazo)\
**Post date:** [21 November 2023 13:27 UTC](https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397/2 "2023-11-21T13:27:18Z")

</div>

Hi,

To day the resolution give 🙃

```auto
nslookup m***y.syncloud.it
Server: 192.168.10.25
Address:	192.168.10.25#53

Non-authoritative answer:
Name:	m***y.syncloud.it
Address: 192.168.1.152

```

I verify in syncloud.it .  
information are good.

Regards.  
Pierre

---

<div class="post-metadata">

**Author:** ![boris](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@boris](https://syncloud.discourse.group/u/boris)\
**Post date:** [21 November 2023 15:22 UTC](https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397/3 "2023-11-21T15:22:33Z")

</div>

Probably that is a slow updating dns server you use (provlbably coming from the ISP), next time try to use one of the public ones, like google 8.8.8.8.

---

<div class="post-metadata">

**Author:** ![pirboazo](https://avatars.discourse-cdn.com/v4/letter/p/a183cd/32.png) [@pirboazo](https://syncloud.discourse.group/u/pirboazo)\
**Post date:** [21 November 2023 15:53 UTC](https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397/4 "2023-11-21T15:53:51Z")

</div>

😌

~ $ nslookup m\*\*\*y.syncloud.it  
Server: 8.8.4.4  
Address: 8.8.4.4#53

Non-authoritative answer:  
Name: m\*\*\*y.syncloud.it  
Address: 192.168.1.152

…

---

<div class="post-metadata">

**Author:** ![pirboazo](https://avatars.discourse-cdn.com/v4/letter/p/a183cd/32.png) [@pirboazo](https://syncloud.discourse.group/u/pirboazo)\
**Post date:** [21 November 2023 15:55 UTC](https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397/5 "2023-11-21T15:55:32Z")

</div>

Same things with 8.8.8.8

nslookup m\*\*\*y.syncloud.it  
Server: 8.8.8.8  
Address: 8.8.8.8#53

Non-authoritative answer:  
Name: m\*\*\*y.syncloud.it  
Address: 192.168.1.152

---

<div class="post-metadata">

**Author:** ![boris](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@boris](https://syncloud.discourse.group/u/boris)\
**Post date:** [21 November 2023 16:24 UTC](https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397/6 "2023-11-21T16:24:13Z")

</div>

so it is all good now?

---

<div class="post-metadata">

**Author:** ![pirboazo](https://avatars.discourse-cdn.com/v4/letter/p/a183cd/32.png) [@pirboazo](https://syncloud.discourse.group/u/pirboazo)\
**Post date:** [21 November 2023 17:30 UTC](https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397/7 "2023-11-21T17:30:56Z")

</div>

No

adresse non routable → RFC1918

```auto
raph@xps13:~$ p3 m***y.syncloud.it
PING m***y.syncloud.it (192.168.1.152) 56(84) bytes of data.

```

I ask at friend to verify…

I have an account on syncloud.it , but can I several device?

In the past that is working.

Pierre

---

<div class="post-metadata">

**Author:** ![boris](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@boris](https://syncloud.discourse.group/u/boris)\
**Post date:** [21 November 2023 17:37 UTC](https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397/8 "2023-11-21T17:37:03Z")

</div>

> adresse non routable → RFC1918

Yes it will work only inside home LAN.  
If you want to have external IP you need to create a port mapping on your router and enable external access in Settings - Access (it will do the port validation for you).

> but can I several device?

Yes you can we have no limitation (if you are not too greedy and start running 100s of devices under one account)

---

<div class="post-metadata">

**Author:** ![pirboazo](https://avatars.discourse-cdn.com/v4/letter/p/a183cd/32.png) [@pirboazo](https://syncloud.discourse.group/u/pirboazo)\
**Post date:** [21 November 2023 17:43 UTC](https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397/9 "2023-11-21T17:43:30Z")

</div>

I don’t understand

The site look at the good address

And if you try to join the external address it s ok.

---

<div class="post-metadata">

**Author:** ![boris](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@boris](https://syncloud.discourse.group/u/boris)\
**Post date:** [21 November 2023 17:49 UTC](https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397/10 "2023-11-21T17:49:38Z")

</div>

All requests are going through the router to the internet so we see your requests are coming from your router’s public IP address (we show it on your device page) but it does not mean anyone can actually connect to your router from outside.

For that you need to create a port mapping and tell the device that this is what you want (enable Settings - Access).

Then DNS will start returning your router IP.

---

<div class="post-metadata">

**Author:** ![pirboazo](https://avatars.discourse-cdn.com/v4/letter/p/a183cd/32.png) [@pirboazo](https://syncloud.discourse.group/u/pirboazo)\
**Post date:** [21 November 2023 19:05 UTC](https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397/11 "2023-11-21T19:05:22Z")

</div>

Hello Boris

I can access at the login page and the setting from my phone.  
With the external IP

SSH work fine also.

Regard  
Pierre

---

<div class="post-metadata">

**Author:** ![boris](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@boris](https://syncloud.discourse.group/u/boris)\
**Post date:** [21 November 2023 20:48 UTC](https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397/12 "2023-11-21T20:48:45Z")

</div>

Did you enable external access in Settings - Access?

---

<div class="post-metadata">

**Author:** ![pirboazo](https://avatars.discourse-cdn.com/v4/letter/p/a183cd/32.png) [@pirboazo](https://syncloud.discourse.group/u/pirboazo)\
**Post date:** [21 November 2023 21:16 UTC](https://syncloud.discourse.group/t/sub-domaine-syncloud-it-cant-be-resolve/397/13 "2023-11-21T21:16:59Z")

</div>

It’s ok 👍🏽👍🏿👍🏽

Thanks