diff --git a/Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md b/Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md
index 050198b..c1baf7b 100644
--- a/Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md	
+++ b/Containers/Kubernetes/Rancher RKE2/Rancher RKE2 Cluster.md	
@@ -61,7 +61,7 @@ kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.6
 helm upgrade -i cert-manager jetstack/cert-manager --namespace cert-manager --create-namespace
 
 # Install Rancher via Helm
-helm upgrade -i rancher rancher-latest/rancher --create-namespace --namespace cattle-system --set hostname=rancher.cyberstrawberry.net --set bootstrapPassword=bootStrapAllTheThings --set replicas=1
+helm upgrade -i rancher rancher-latest/rancher --create-namespace --namespace cattle-system --set hostname=rancher.bunny-lab.io --set bootstrapPassword=bootStrapAllTheThings --set replicas=1
 
 # Install Longhorn via Helm
 helm upgrade -i longhorn longhorn/longhorn --namespace longhorn-system --create-namespace
@@ -69,7 +69,7 @@ helm upgrade -i longhorn longhorn/longhorn --namespace longhorn-system --create-
 
 !!! note
     Be sure to write down the "*bootstrapPassword*" variable for when you log into Rancher later.  In this example, the password is `bootStrapAllTheThings`.
-    Also be sure to adjust the "*hostname*" variable to reflect the FQDN of the cluster.  This is important for the last step where you adjust DNS.  The example given is `rancher.cyberstrawberry.net`.
+    Also be sure to adjust the "*hostname*" variable to reflect the FQDN of the cluster.  This is important for the last step where you adjust DNS.  The example given is `rancher.bunny-lab.io`.
 
 ## Create Additional ControlPlane Node(s)
 This is the part where you can add additional controlplane nodes to add additional redundancy to the RKE2 Cluster.  This is important for high-availability environments.
@@ -125,12 +125,12 @@ systemctl start rke2-agent.service
 ```
 
 ## DNS Server Record
-You will need to set up some kind of DNS server record to point the FQDN of the cluster (e.g. `rancher.cyberstrawberry.net`) to the IP address of the Initial ControlPlane.  This can be achieved in a number of ways, such as editing the Windows `HOSTS` file, Linux's `/etc/resolv.conf` file, a Windows DNS Server "A" Record, or an NGINX/Traefik Reverse Proxy.
+You will need to set up some kind of DNS server record to point the FQDN of the cluster (e.g. `rancher.bunny-lab.io`) to the IP address of the Initial ControlPlane.  This can be achieved in a number of ways, such as editing the Windows `HOSTS` file, Linux's `/etc/resolv.conf` file, a Windows DNS Server "A" Record, or an NGINX/Traefik Reverse Proxy.
 
 Once you have added the DNS record, you should be able to access the login page for the Rancher RKE2 Kubernetes cluster.  Use the `bootstrapPassword` mentioned previously to log in, then change it immediately from the user management area of Rancher.
 
 | TYPE OF ACCESS | FQDN                                  | IP ADDRESS   | 
 | -------------- | ------------------------------------- | ------------ |
-| HOST FILE      | rancher.cyberstrawberry.net           | 192.168.3.21 |
-| REVERSE PROXY  | http://rancher.cyberstrawberry.net:80 | 192.168.5.29 |
-| DNS RECORD     | A Record: rancher.cyberstrawberry.net | 192.168.3.21 |
\ No newline at end of file
+| HOST FILE      | rancher.bunny-lab.io           | 192.168.3.10 |
+| REVERSE PROXY  | http://rancher.bunny-lab.io:80 | 192.168.5.29 |
+| DNS RECORD     | A Record: rancher.bunny-lab.io | 192.168.3.10 |
\ No newline at end of file