{{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.