There area unit 2 aspects you'll need to consider:
each names should resolve to an equivalent IP addresse (i.e. same webserver)
webserver should associate request names to either hostname with an equivalent set of sites
It appears that you just have managed the primary half, which is, fitting nameservers specified hosts in each zones resolve to the proper IP addresses. currently you most likely need to line up your webserver such, that notwithstanding what name the pages area unit requested as, area unit each crystal rectifier to an equivalent pages.
i am unsure a way to do the second half. ought to it's through edits to the Zone File? forgive my clumsiness, i am a beginner at this. Ohio and by the method, whereas creating a Reverse IP Domain Check I detected plenty web sites|of internet sites} hosted on an equivalent webserver as my website exploitation an equivalent IP. therefore perhaps exploitation AN A airt inform to it IP isn't the neatest thanks to get laid. – oquiroz Jul sixteen at 4:47
unlikely. The second half is webserver setup, not nameserver setup. If several names should reference an equivalent webpages, you always try this by configuring the "default" webserver, that is that the same one describing the document root used once requesting pages with the IP address given as hostname within the uniform resource locator. apache2 users would realize this configuration ordinarily at /etc/apache2/sites-available/default - with a "panel" sitting between user and configuration, the placement of configuration could also be hidden from you, and that i don't have any plan wherever to seem for this setup during a "panel" – Deleted User Jul sixteen at 9:40
With "shared hosting" style of net servers, you cannot management the default webserver - you'd have a VirtualHost style of setup, within which you'll list aliases of hostnames, therefore the webserver is aware of that names in page requests a specific VirtualHost configuration should be used. Even in those setups the hostnames should resolve to AN IP address eventually, so AN A record continues to be the thanks to go. The request name are a part of the page request, therefore the webserver is aware of from the request what VirtualHost to reference. – Deleted User Jul sixteen at 9:46
Finally created it! i could not realize the way to directly edit the apache2 configuration in this electrical device. however I detected that GoDaddy's awful domain electrical device has AN choice to create a redirection from a subdomain to any uniform resource locator i need (is that a cname record?) through a 301 or 302 redirection. therefore I created it and everything is functioning fine now! Thanks plenty for the help! – oquiroz Jul nineteen at 21:53
no, that is not a CNAME record - that is a protocol redirect: requests go 1st to their webserver, that then tells webclients "go elsewhere". A CNAME record can eventually resolve to AN IP address, like AN A record will - however with level of indirection. Therefore, from partitioning viewpoint, a CNAME does not provide you with something further. it's simply AN instrument meant for aiding once the A record it points to isn't inside your management. –