diff --git a/README.md b/README.md
index 61099c7..fc92bef 100644
--- a/README.md
+++ b/README.md
@@ -20,5 +20,8 @@ vagrant up --provision-with setup app
 ### Subsequent Runs
 Once you already have everything setup for the app, you can simply run `vagrant up`. If you only need the application, and have your own SQL server, redis, and mailhog (or some combination), you can run `vagrant up [boxes]` and replace `[boxes]` with the boxes to bring online.
 
+### Daemons
+There are VMs for both, the old and the new, daemons configured. They do not start automatically. You can start them using `vagrant up daemon` (for the nodejs one) and `vagrant up wings` (the golang one).
+
 ### Updating /etc/hosts
 On your first run, and whenever the hostnames change, you'll have to run `vagrant hostmanager app --provider docker` to update your /etc/hosts file.
diff --git a/Vagrantfile b/Vagrantfile
index 469ffc6..24f920f 100644
--- a/Vagrantfile
+++ b/Vagrantfile
@@ -157,7 +157,7 @@ Vagrant.configure("2") do |config|
 	# Create a docker container for mailhog which providers a local SMTP environment that avoids actually
 	# sending emails to the address.
 	config.vm.define "mailhog" do |mh|
-		mh.vm.hostname = "mailhog.pterodactl.test"
+		mh.vm.hostname = "mailhog.pterodactyl.test"
 		mh.vm.synced_folder ".", "/vagrant", disabled: true
 
 		mh.vm.network "forwarded_port", guest: 1025, host: 1025