The WWW record is wrong, it should not be www.domain.com CNAME domain, it should be www CNAME domain. WWW then should have an A record, www.domain.com IN A ip
This btw fixes many things and provides a more efficient server. It cuts back on requests by HALF, and also requires less CPU time and less bandwidth.
Just FYI
And if anyone knows where I can find the templates… I’m not all that familiar with tinydns, just bind
Thanks ahead of time.
Btw, what needs to be edited is the WWW settings…
www should get 1 change to www without the domain, and then another line added for an A record.
This is a little bit more complicated than I thought.
The DNS templates need to be modified quite a bit, because all sub domains get added improperly.
All subdomains need a cname for just the plain subdomain, to the top domain… and then need the fqdn (subdomain.domain.com) to be assigned an A entry with the ip address…
and your browser makes a query to it (you put in www.domain.com in your browser), then your browser has to make TWO queries to that domain, one to find out www.domain.com points to domain.com and another to find out what ip address domain.com points to.
I agree that in theory, using an “A” record could be considered better, although I don’t know if there is an actual noticable difference in practice. Of all the hosting related processes running on your server, tinydns is probably the least resource intensive of them all - I’ve never seen tinydns use more than a fraction of a percent of CPU even on extremely busy tinydns DNS servers. That combined with caching nameservers used all over the place drops the number of requests to the main dns servers for your domain even lower.
DNS templates will be available in the upcoming release, so making this change will be easy soon.
I have a question regarding your proposed change, what purpose does the: