User:Qw7402 - Revision history

Qw7402 at 16:12, 12 March 2026

2026-03-12T16:12:00Z

← Older revision		Revision as of 16:12, 12 March 2026
Line 14:		Line 14:


	IPv6: yes		IPv6-addresses: yes

	IPv4: no		IPv4-addresses: no

	By default every VM will receive a private IPv4 ~~Address~~. Egress IPv4 connectivity is provided via SNAT.		By default every VM will receive a private IPv4-addresses. Egress IPv4 connectivity is provided via SNAT.

	'''📌 Note:''' IPv4 ingress connectivity is also possible in every region via request.		'''📌 Note:''' IPv4 ingress connectivity is also possible in every region via request.

Qw7402 at 16:10, 12 March 2026

2026-03-12T16:10:53Z

← Older revision		Revision as of 16:10, 12 March 2026
Line 2:		Line 2:
	{{InANutshell\|		{{InANutshell\|
	<li>Each bwCloud-OS instance launched using the standard method is automatically assigned a <strong>public IP address</strong>.</li>		<li>Each bwCloud-OS instance launched using the standard method is automatically assigned a <strong>public IP address</strong>.</li>
	<li>Instances are also assigned a <strong>persistent FQDN</strong> based on their ~~UUID~~ and region.</li>		<li>Instances are also assigned a <strong>persistent FQDN</strong> based on their name, project and region.</li>
	<li>Domain hosting is not provided, but you can point your own <strong>domain</strong> to the instance’s FQDN using a CNAME record.</li>		<li>Domain hosting is not provided, but you can point your own <strong>domain</strong> to the instance’s FQDN using a CNAME record.</li>
	}}		}}
Line 14:		Line 14:


	V6: yes		IPv6: yes

	V4: no		IPv4: no

	By default every VM will receive a private V4 Address. Egress V4 connectivity is provided via SNAT.		By default every VM will receive a private IPv4 Address. Egress IPv4 connectivity is provided via SNAT.

	'''📌 Note:''' V4 ingress connectivity is also possible in every region via request.		'''📌 Note:''' IPv4 ingress connectivity is also possible in every region via request.

	'''📌 Note:''' Each '''region''' in bwCloud-OS has its '''own set of IP address ranges.'''		'''📌 Note:''' Each '''region''' in bwCloud-OS has its '''own set of IP address ranges.'''
Line 38:		Line 38:
	Yes.		Yes.

	Floating IPs provide a mechanism to 1:1 NAT a public V4 addresse to a private V4 address of an instance enabling ingress v4 connectivity.		Floating IPs provide a mechanism to 1:1 NAT a public IPv4 addresse to a private IPv4 address of an instance enabling ingress IPv4 connectivity.

	For more information and detailed setup instructions, see the guide below.		For more information and detailed setup instructions, see the guide below.
Line 67:		Line 67:
	Yes.		Yes.

	We manage the ~~TLD~~ <code>bwcloud-os-instance.de.</code> It is possible to request a DNS record for a floating IP for example.		We manage the top level domain <code>bwcloud-os-instance.de.</code> It is possible to request a DNS record for a floating IP for example.

	== Can I get a custom domain via bwCloud-OS? ==		== Can I get a custom domain via bwCloud-OS? ==

Qw7402 at 16:05, 12 March 2026

2026-03-12T16:05:14Z

← Older revision		Revision as of 16:05, 12 March 2026
Line 67:		Line 67:
	Yes.		Yes.

	We manage the TLD bwcloud-os-instance.de. It is possible to request a DNS record for a floating IP for example.		We manage the TLD <code>bwcloud-os-instance.de.</code> It is possible to request a DNS record for a floating IP for example.

	== Can I get a custom domain via bwCloud-OS? ==		== Can I get a custom domain via bwCloud-OS? ==

Qw7402 at 15:12, 12 March 2026

2026-03-12T15:12:29Z

← Older revision		Revision as of 15:12, 12 March 2026
Line 60:		Line 60:
	'''Example:'''		'''Example:'''

	If your instance name is ~~'''~~kos~~'''~~, the project is called ~~'''~~yarn~~'''~~ and it runs in Mannheim (<code>ma</code>), the FQDN will be:<pre>kos.yarn.vm.ma.bwcloud-os-instance.de.</pre>The FQDN can also be found in the '''[https://portal.bw-cloud.org/ Dashboard]''', on the '''Instances''' -> '''Network''' -> '''Interface''' page.		If your instance name is <code>kos</code>, the project is called <code>yarn</code> and it runs in Mannheim (<code>ma</code>), the FQDN will be:<pre>kos.yarn.vm.ma.bwcloud-os-instance.de.</pre>The FQDN can also be found in the '''[https://portal.bw-cloud.org/ Dashboard]''', on the '''Instances''' -> '''Network''' -> '''Interface''' page.

	== Can I get a request more DNS records in bwCloud-OS? ==		== Can I get a request more DNS records in bwCloud-OS? ==

Qw7402 at 15:11, 12 March 2026

2026-03-12T15:11:26Z

← Older revision		Revision as of 15:11, 12 March 2026
Line 54:		Line 54:

	* The '''UUID''' '''of the instance'''		* The '''UUID''' '''of the instance'''
	* The project name		* The '''project name'''
	* The '''region abbreviation''' (e.g., <code>ma</code> for Mannheim)		* The '''region abbreviation''' (e.g., <code>ma</code> for Mannheim)
	* The '''domain suffix''': <code>.bw-cloud-instance.org</code>		* The '''domain suffix''': <code>.bw-cloud-instance.org</code>
Line 60:		Line 60:
	'''Example:'''		'''Example:'''

	If your instance name is kos, the project is called yarn and it runs in Mannheim (<code>ma</code>), the FQDN will be:<pre>kos.yarn.vm.ma.bwcloud-os-instance.de.</pre>The FQDN can also be found in the '''[https://portal.bw-cloud.org/ Dashboard]''', on the '''Instances''' -> Network ->Interface page.		If your instance name is '''kos''', the project is called '''yarn''' and it runs in Mannheim (<code>ma</code>), the FQDN will be:<pre>kos.yarn.vm.ma.bwcloud-os-instance.de.</pre>The FQDN can also be found in the '''[https://portal.bw-cloud.org/ Dashboard]''', on the '''Instances''' -> '''Network''' -> '''Interface''' page.

	== Can I get a request more DNS records in bwCloud-OS? ==		== Can I get a request more DNS records in bwCloud-OS? ==
Line 84:		Line 84:
	The instance’s FQDN is based on its UUID and region. Since the UUID is persistent for the instance's lifetime (even if the instance is stopped and started again), you can safely set a CNAME record like:		The instance’s FQDN is based on its UUID and region. Since the UUID is persistent for the instance's lifetime (even if the instance is stopped and started again), you can safely set a CNAME record like:

	<code>myvm.example.org → ~~uuid~~.region.bw-~~cloud~~-instance.~~org~~</code>		<code>myvm.example.org → instance-name.project-name.vm.region.bwcloud-os-instance.de</code>

	==== 🔹 Dynamic DNS ====		==== 🔹 Dynamic DNS ====

Qw7402 at 15:02, 12 March 2026

2026-03-12T15:02:34Z

← Older revision		Revision as of 15:02, 12 March 2026
Line 12:		Line 12:

	== Will my instance receive a public IP? ==		== Will my instance receive a public IP? ==
	~~<span id="Public-IPs"></span>~~
	~~Yes. By default, every instance launched using the standard method in bwCloud-OS is automatically assigned a '''publicly accessible IP address'''.~~

	'''Note:''' Each '''region''' in bwCloud-OS has its '''own set of IP address ranges.'''
			V6: yes

			V4: no

			By default every VM will receive a private V4 Address. Egress V4 connectivity is provided via SNAT.

			'''📌 Note:''' V4 ingress connectivity is also possible in every region via request.

			'''📌 Note:''' Each '''region''' in bwCloud-OS has its '''own set of IP address ranges.'''

	== How long does an IP remain assigned to my instance? ==		== How long does an IP remain assigned to my instance? ==
	<span id="Public-IP-Liftime"></span>		<span id="Public-IP-Liftime"></span>

	The ~~public~~ IP address(es''')''' assigned to your instance remains associated with it for the entire lifetime of the instance — even if you stop (shut down) the instance.		The IP address(es''')''' assigned to your instance remains associated with it for the entire lifetime of the instance — even if you stop (shut down) the instance.

	The IP is only released when the instance is deleted (terminated). After termination, the IP is returned to the regional pool and may be reassigned to another instance in the region.		The IP is only released when the instance is deleted (terminated). After termination, the IP is returned to the regional pool and may be reassigned to another instance in the region.

	'''📌 Note:''' ~~The rules for assigning public~~ IPs to ~~instances are currently under revision, so persistent public IPs cannot~~ be ~~guaranteed in the future. It is recommended to use [[Networks#FQDN\|FQDNs]] instead~~.		'''📌 Note:''' Floating IPs will remain even after an Instance deletion. They have to be released manually.

	== Are Floating IPs also available for instances? ==		== Are Floating IPs also available for instances? ==
	<span id="Floating-IPs"></span>		<span id="Floating-IPs"></span>

	Yes~~, but currently not in all regions~~.		Yes.

	~~'''📌 Note:'''~~ Floating IPs ~~are planned for all regions after the next major software upgrade in 2026~~.		Floating IPs provide a mechanism to 1:1 NAT a public V4 addresse to a private V4 address of an instance enabling ingress v4 connectivity.

	For more information and detailed setup instructions, see the guide below.		For more information and detailed setup instructions, see the guide below.
Line 53:		Line 60:
	'''Example:'''		'''Example:'''

	If your instance name is kos, the project is called yarn and it runs in Mannheim (<code>ma</code>), the FQDN will be:<pre>kos.yarn.vm.ma.bwcloud-os-instance.de.</pre>		If your instance name is kos, the project is called yarn and it runs in Mannheim (<code>ma</code>), the FQDN will be:<pre>kos.yarn.vm.ma.bwcloud-os-instance.de.</pre>The FQDN can also be found in the '''[https://portal.bw-cloud.org/ Dashboard]''', on the '''Instances''' -> Network ->Interface page.

			== Can I get a request more DNS records in bwCloud-OS? ==


	~~'''Retrieval''': From '''inside the instance,''' the FQDN can be determined by:~~		Yes.

	~~<pre>REGION="ma"~~		We manage the TLD bwcloud-os-instance.de. It is possible to request a DNS record for a floating IP for example.
	~~FQDN="$(cat /var/lib/cloud/data/instance~~-~~id).${REGION}.bw-cloud~~-instance.~~org"</pre>The FQDN can also be found in the '''[https://portal.bw-cloud~~.~~org/ Dashboard]''', on the '''Instances''' page~~.

	== Can I get a domain via bwCloud-OS? ==		== Can I get a custom domain via bwCloud-OS? ==
	<span id="Domains"></span>		<span id="Domains"></span>

Qw7402 at 12:55, 11 March 2026

2026-03-11T12:55:37Z

← Older revision		Revision as of 12:55, 11 March 2026
Line 47:		Line 47:

	* The '''UUID''' '''of the instance'''		* The '''UUID''' '''of the instance'''
			* The project name
	* The '''region abbreviation''' (e.g., <code>ma</code> for Mannheim)		* The '''region abbreviation''' (e.g., <code>ma</code> for Mannheim)
	* The '''domain suffix''': <code>.bw-cloud-instance.org</code>		* The '''domain suffix''': <code>.bw-cloud-instance.org</code>
Line 52:		Line 53:
	'''Example:'''		'''Example:'''

	If your instance ~~UUID~~ is ~~<code>caffee-4242-2323-caffee</code>~~ and it runs in Mannheim (<code>ma</code>), the FQDN will be:<pre>~~caffee-4242-2323-caffee~~.ma.bw-~~cloud~~-instance.~~org~~</pre>		If your instance name is kos, the project is called yarn and it runs in Mannheim (<code>ma</code>), the FQDN will be:<pre>kos.yarn.vm.ma.bwcloud-os-instance.de.</pre>

	'''Retrieval''': From '''inside the instance,''' the FQDN can be determined by:		'''Retrieval''': From '''inside the instance,''' the FQDN can be determined by:

Qw7402: Created page with " {{InANutshell|
Each bwCloud-OS instance launched using the standard method is automatically assigned a public IP address.

Instances are also assigned a persistent FQDN based on their UUID and region.

Domain hosting is not provided, but you can point your own domain to the instance’s FQDN using a CNAME record.
}} TOC = Networks & IP-addresses = == Wi..."

2026-03-11T12:37:31Z

Created page with " {{InANutshell| <li>Each bwCloud-OS instance launched using the standard method is automatically assigned a public IP address.</li> <li>Instances are also assigned a persistent FQDN based on their UUID and region.</li> <li>Domain hosting is not provided, but you can point your own domain to the instance’s FQDN using a CNAME record.</li> }} __TOC__ = Networks & IP-addresses = == Wi..."

New page

{{InANutshell|
<li>Each bwCloud-OS instance launched using the standard method is automatically assigned a public IP address.</li>
<li>Instances are also assigned a persistent FQDN based on their UUID and region.</li>
<li>Domain hosting is not provided, but you can point your own domain to the instance’s FQDN using a CNAME record.</li>
}}

__TOC__

= Networks & IP-addresses =

== Will my instance receive a public IP? ==

Yes. By default, every instance launched using the standard method in bwCloud-OS is automatically assigned a '''publicly accessible IP address'''.

'''Note:''' Each '''region''' in bwCloud-OS has its '''own set of IP address ranges.'''

== How long does an IP remain assigned to my instance? ==


The public IP address(es''')''' assigned to your instance remains associated with it for the entire lifetime of the instance — even if you stop (shut down) the instance.

The IP is only released when the instance is deleted (terminated). After termination, the IP is returned to the regional pool and may be reassigned to another instance in the region.

'''📌 Note:''' The rules for assigning public IPs to instances are currently under revision, so persistent public IPs cannot be guaranteed in the future. It is recommended to use [[Networks#FQDN|FQDNs]] instead.

== Are Floating IPs also available for instances? ==


Yes, but currently not in all regions.

'''📌 Note:''' Floating IPs are planned for all regions after the next major software upgrade in 2026.

For more information and detailed setup instructions, see the guide below.

➡️ [[Guide: Routers and Floating IPs|Routers and Floating IPs Guide]].

= Domains and FQDNs =

== Does bwCloud-OS also assign FQDNs? ==


Yes. Every running instance in bwCloud-OS is automatically assigned a '''generic hostname (FQDN)'''. This allows the instance to be reached via a '''persistent network identifier''', even if its public IP address changes. This FQDN is valid for the '''lifetime''' of the instance.

==== Format of the instance's FQDN ====

* The '''UUID''' '''of the instance'''
* The '''region abbreviation''' (e.g., <code>ma</code> for Mannheim)
* The '''domain suffix''': <code>.bw-cloud-instance.org</code>

'''Example:'''

If your instance UUID is <code>caffee-4242-2323-caffee</code> and it runs in Mannheim (<code>ma</code>), the FQDN will be:<pre>caffee-4242-2323-caffee.ma.bw-cloud-instance.org</pre>

'''Retrieval''': From '''inside the instance,''' the FQDN can be determined by:

<pre>REGION="ma"
FQDN="$(cat /var/lib/cloud/data/instance-id).${REGION}.bw-cloud-instance.org"</pre>The FQDN can also be found in the '''[https://portal.bw-cloud.org/ Dashboard]''', on the '''Instances''' page.

== Can I get a domain via bwCloud-OS? ==


No, bwCloud-OS does '''not''' provide custom '''domain hosting'''. However, you can use your '''own domain''' — either through your home institution or an external domain provider — to '''point to your instance'''.

Some options are described below.

== How can I point a domain to an instance? ==


You can point a domain to your instance in two main ways:

==== 🔹 CNAME to the instance FQDN ====
The instance’s FQDN is based on its UUID and region. Since the UUID is persistent for the instance's lifetime (even if the instance is stopped and started again), you can safely set a CNAME record like:

<code>myvm.example.org → uuid.region.bw-cloud-instance.org</code>

==== 🔹 Dynamic DNS ====
Alternatively, you can configure a Dynamic DNS setup where your VM updates its IP in a third-party DNS service — especially if you don’t have your own domain, or your use case involves frequently changing or multiple IPs.

== Can I get a certificate from bwCloud-OS? ==


No, bwCloud-OS does '''not''' provide '''certificates.''' However, you can obtain certificates directly from public providers like '''Let’s Encrypt''' using tools such as '''Certbot''', which you install and run on your instance.