Change default domain suffix for new sites from .dev to .test


#1

Google Chrome is soon going to implement a feature whereby all requests to .dev domains will be automatically redirected to https. This is because the .dev gTLD is owned by Google.

As recommended in that article, I think that Local should therefore not use .dev as the default extension for new sites, but use .test instead because .test is reserved for testing and development purposes.


Change the default TLD when creating new sites
.dev domain doesn't work
Can't access Local site after cloning
Local does not work with Chrome, only Safari and Firefox on Mac
#2

This is becoming a major issue now, cannot use Chrome to test flywheel sites as redirecting then get an icann name clash error.

How can we change .dev to .local or .test?


#3

How about .fly (except of course google owns that one too!)


#4

I don’t think anyone is listening here guys :frowning:


#5

Hey all,

.local is the new TLD as of the Local 2.1.0 pre-release.


Of course we are! :wink:


#6

Haa haa knew you would come back to me :wink:


#7

@clay I don’t think that using .local is a good choice, as reported here, .local has a very specific purpose and .test would be the right choice to do.

As reported above, I think Apple uses .local for bonjour services on macOS, which could cause potential conflicts.
https://support.apple.com/en-gb/HT203136

At least we should have the chance to change this globally in the preferences of the app, and not only every time we start a new local website.


#8

I agree. I use .test for all mine now.


#9

Hi @valentinocossar,

I really appreciate the info!

Just so it’s out there, we decided to go with .local since it’s officially a special-use domain and not resolvable at this time. Considering this, I don’t think we’ll see something like what we saw with .dev and .foo. Also, Local automatically adds IPv4 and IPv6 (as of 2.2.0+) hosts entries that should negate any possible issues with DNS conflicts. Finally, we eventually landed on it for branding purposes. :slight_smile:

With that said, I’ve made a note to add an option to change the default TLD in Local so we can all use what we prefer. :smiley:


#10

Thank you for the explanation, I appreciate that you are considering to add an option to change the default TLD globally in Local. :smile:


#11

Hey all,

Just wanted to give you a heads up that 2.2.4 is now available and includes an option to change the default TLD. :smiley:


#12

I spotted that in the new release, thanks so much for including it :slight_smile: