DNS seed nodes are intended to identify a set of nodes to connect to the network when the wallet is unable to connect and have never been connected. In that case the client issues DNS requests to get the list of other peer addresses.
Here is the list of host names that every Crown client includes:
Seed nodes are running on VPS servers. Here is the list of ip addresses
The process of running DNS seed nodes includes two parts:
Running last version of crownd
Running dnsseed (with arguments)
Update DNS seed node
To update Crown wallet on DNS seed node that's enough to download the latest version of Crown and extract bin/* under /usr/local/bin/
Here is the example of simple command which does everything rm -rf Crown-Linux64.zip; rm -rf 842.5-x86_64-unknown-linux-gnu; wget https://github.com/Crowndev/crowncoin/releases/download/v0.12.4.1/Crown-Linux64.zip; unzip Crown-Linux64.zip; cp -rf 842.5-x86_64-unknown-linux-gnu/bin/* /usr/local/bin/; cp -rf 842.5-x86_64-unknown-linux-gnu/lib/* /usr/local/lib/
"842.5-x86_64-unknown-linux-gnu" and "v0.12.4.1" need to be changed accordingly.
'dnsseed' executable doesn't need to be updated with Crown version change but only when protocol version is changed (for example 70051 to 70052) which is rare (mostly before official hard fork release).
Here is the DNS seed repository on github -https://github.com/Crowndev/crown-seeder
Every DNS node has crown-seeder cloned from github so after making according changes on remote repository we can do
cd crown-seedergit pullmakecp dnsseed /usr/local/bin/
After the above mentioned steps it's enough to reboot DNS seed VPS it will run both executables during boot.