Frequently Asked Questions

The NearlyFreeSpeech.NET FAQ (*)

Domain Name Service (DNS) (*)

How come www.example.com works but example.com does not?

Why are my active and authoritative name servers different?

How should I configure my third-party DNS to point to my site?

What name servers should I use with my domain?

How do I add NearlyFreeSpeech.NET DNS for a new domain name to my existing website?

I already have NearlyFreeSpeech.NET DNS for www.example.com. Will it cost more to add another.example.com (or example.com)?

How do I use a domain I registered elsewhere with NearlyFreeSpeech.NET DNS?

I have NearlyFreeSpeech.NET DNS set up. How do I add a new site using a subdomain?

How do I configure NearlyFreeSpeech.NET DNS to work with my third-party email service?

What are the IP address(es) listed for my site used for? Are they name servers?

What is the "SPF Email Protection" option for DNS?

How do I add / remove DNS records for my domain?

How do I change the name servers for a domain registered with NearlyFreeSpeech.NET?

Do you support wildcard DNS?

How come I can't remove that DNS record?

If I set up DNS for more than one domain, will they all use the same name servers?

Can I get secondary DNS in another location?

How do I point a NearlyFreeSpeech.NET DNS record at my dynamic home IP address?

Are you yes-www or no-www?

We are strongly yes-www. (There used to be a site in favor of no-www, but it went away. I guess yes-www is winning.)

Using URLs with bare domains (like https://example.com/) creates a number of problems, and we strongly recommend that you avoid it for anything other than redirecting to the real web site (like www.example.com).

Some of the limitations are:

Despite the drawbacks, this is something that visitors to your site expect to work and we know that.

The best compromise is to redirect visitors from example.com to your www.example.com alias. To do that, add both www.example.com and example.com as aliases to your site and (unless you are using WordPress) enable the hard canonical type setting. If you are using WordPress, it will manage your host names automatically, and you should set the site's canonical type to off (the default).

There are, of course, exceptions; this is more of a guideline than an actual rule. It may make sense to forego the www for a business website if the web site is the business. Sites with very short names are also perpetually trendy, and knocking "www." off the front in service of shortness is definitely one way to chase that trend.

If you're sure you're an exception, apply these recommendations in reverse to direct visitors from www.example.com to example.com.