Catch-all records are not to be advised. Use a CNAME for www subdomain pointing to the base domain, rather than another A record (easier maintenance... CNAME are here for a reason!).
Definitely not a nginx problem though... --- *B. R.* On Mon, May 18, 2015 at 8:07 AM, Nikolaj Schomacker <[email protected]> wrote: > You need to point www.inplanesight.org to the same IP as inplanesight.org. > > You can also make an A record in your DNS for *.inplanesigt.org which > will act as a "catch all" for any subdomain. > > On Mon, May 18, 2015 at 1:54 AM Reinis Rozitis <[email protected]> wrote: > >> > Well this looks so simple in the nginx manual. I have cleared the >> browser >> > cache. so I am running out of simple idea. The domain is >> inplanesight.org. >> > http://www.inplanesight.org will 404 >> > http://inplanesight.org works fine >> >> It's a dns problem - www.inplanesight.org doesn't resolve >> http://www.dnswatch.info/dns/dnslookup?host=www.inplanesight.org >> >> rr >> >> _______________________________________________ >> nginx mailing list >> [email protected] >> http://mailman.nginx.org/mailman/listinfo/nginx >> > > _______________________________________________ > nginx mailing list > [email protected] > http://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
