Custom domains

Learn how using your custom domain with Nearest!

You need to activate your app to use the custom domain feature. Please activate app and return adding a custom domain.

Nearest! can either be operated as a subdomain (i.e. locations.brand.com) or as a root domain (i.e. locator.io). All you have to do is add or customize a CNAME or A record in your DNS server and enter your custom domain.

We highly recommend using a custom domain with Nearest! even if you wont use the Nearest! stand-alone web-app. Read more why...

Adding records to your DNS

Changes to the DNS can lead to unavailability of the entire domain and should only be performed by system administrators or devops.

A-Record

Subdomain (locations.brand.com)

subdomain           IN  A     136.243.94.96             ; IPv4 address for subdomain.example.com
subdomain           IN  AAAA  2a01:4f8:171:6df::2       ; IPv6 address for subdomain.example.com

Root domain (locator.io)

@                   IN  A     136.243.94.96             ; IPv4 address for example.com
@                   IN  AAAA  2a01:4f8:171:6df::2       ; IPv6 address for example.com
www                 IN  A     136.243.94.96             ; IPv4 address for www.example.com
www                 IN  AAAA  2a01:4f8:171:6df::2       ; IPv6 address for www.example.com

CNAME-Record

Subdomain (locations.brand.com)

subdomain          IN  CNAME finder.nearest.place.      ; record for subdomain.example.com

Add your custom domain

After adding your DNS records got to Interface > Web-app > Domain and enter your custom domain. We will check your DNS settings, register SSL and activate your domain to our server.

Why you should use a custom domain?

As mentioned above, it is highly recommended to use a custom domain with Nearest!. Otherwise the following unwanted scenarios will happen and harm the user experience:

  • Unwanted ranking of your-nearest-id.nearest.place in the search engine results with your keywords

  • User will be asked from the browser, to share its location with your-nearest-id.nearest.place which can be confusing when implemented into your existing website / domain.

PreviousWebappNextCustomizations

Last updated