Resolved 403 Forbidden

[tcsigmo2]

So I have an addon top-level domain that is connected to my account and my public_html folder is empty. I added the DNS records to verify the domain ownership with google webmaster and google webmaster says it is verified after I add the cname record. So on google sites I add the custom domain as www.(my domain) except with my actual domain. After I add the custom domain to google sites I go to the website and it says
"Forbidden
You don't have permission to access this resource."
so I'm not sure what I did wrong, I even tried using a different subdomain other than www and adding a .htaccess file but I get the same message, I don't see why I would need an index page in Public_html if I'm just using the cname www to point to google verification as opposed to an a record pointing to the IP address of the server.

 

[garrettroyce]

There are two possibilities;

You have not turned on

Options +Indexes

in your .htaccess file. To prevent malicious crawlers and etc. from logging your filesystem data, Indexes is generally preferred to be off. You would require an index.(something) file to get rid of this error as long as (something) is a valid extension; usually .html, .htm, or .php .

Your folder or file permissions are not set correctly.

Folders should be 755 permissions (owner - all, others - read/execute) and files should be 644 (owner read/write, others read only)

 

[tcsigmo2]

There are two possibilities;

You have not turned on

Options +Indexes

in your .htaccess file. To prevent malicious crawlers and etc. from logging your filesystem data, Indexes is generally preferred to be off. You would require an index.(something) file to get rid of this error as long as (something) is a valid extension; usually .html, .htm, or .php .

Your folder or file permissions are not set correctly.

Folders should be 755 permissions (owner - all, others - read/execute) and files should be 644 (owner read/write, others read only)

this hasn't made my google site accessible from my domain, it has only made it so that my index.html file is displayed at the domain

 

[Anna]

Let's see if I get this correct.

You have domain added to your account, that you want to display content you have on google sites rather then content you have with us?

As long as the domain point to our server, it will display what is associated with the domain on our server.

You would need to point, by A record I assume, the domain to google sites in some way, or I'd suggest looking into adding the domain to google domains rather then use us as the DNS manager (there are also a lot of services out there that handles only DNS if you can't add it to google domains). Our service is intended for use with a site you host with us.

And yes, www won't work as it has been removed from the DNS of your domain, it has to be listed there as it is in all aspects the same as any other subdomain except for the fact that it's natural behavior is to be an alias of the base domain without www.

 

[tcsigmo2]

Let's see if I get this correct.

You have domain added to your account, that you want to display content you have on google sites rather then content you have with us?

As long as the domain point to our server, it will display what is associated with the domain on our server.

You would need to point, by A record I assume, the domain to google sites in some way, or I'd suggest looking into adding the domain to google domains rather then use us as the DNS manager (there are also a lot of services out there that handles only DNS if you can't add it to google domains). Our service is intended for use with a site you host with us.

And yes, www won't work as it has been removed from the DNS of your domain, it has to be listed there as it is in all aspects the same as any other subdomain except for the fact that it's natural behavior is to be an alias of the base domain without www.

so is it not possible for me to use this service to manage dns on some subdomains as well as host content on others because I wanted to do both since I can't do that with just my domain host.

 

[Anna]

If you intend to use the service here for a site, indeed you can.

You do need to add the subdomains to DNS (DNS Management) though and point it to the other service though for it to work.

if you for instance would want second.mydomain.com (or www.mydomain.com) to point to IP 127.3.3.87 (not a valid IP) you would go to DNS Management and add it
with an A record for that domain, if the subdomain doesn't exist in DNS configuration it won't work, see:
https://www.screencast.com/t/Yku7oQORYaof