sorry i gave the wrong path... my temp files are actually in: /var/www/html/temp/a.html /var/www/html/temp/b.html (maybe i'm not suppose to put anything under /var/www/html in the first place?) in any case, no, there is no .htaccess file in /var/www/ or /var/www/*
The folder /var/www/html is not configured and not supported by ISPCOnfig. You wull have to create a website in ISPCOnfig and put your files in the website folder that ISPCOnfig creates for the website.
ok thanks... i have www.example.com pointed correctly to my ispconfig box (DNS hosted by my isp) i can access my control panel using https://www.example.com:81 can i create sub1.example.com using ispconfig? can i expect that website (http://sub1.example.com) and email ([email protected]) to work? thanks
i created a "site" hostname=sub1 and domain=example.com i tick the "DNS" and "DNS-MX" boxes... i've also created a user in this site (sub1.example.com) when i go to the DNS section, i see that there is an existing ========================================= domain (SOA) = example.com IP = mypublicIP nameserver1 = example.com nameserver2 = example.com under "records": A record - IPAddr=myPublicIP, hostname=sub1 MX record - mailserver=example.com, hostname=sub1 ========================================= i'm not sure this SOA record is correctly created by myself earlier, or created by ispconfig after i add the new site sub1 but problem now is that i can't ping sub1.example.com is it due to my TTL? or is it to do with the my ISP who is hosting example.com (or do i need to restart some process) thanks!!
i have registered a new domain example2.com with godaddy.com i want to host this new domain on my ispconfig server (example.com) however, when i try to point the DNS of example2.com to example.com, godaddy gives an error, "Unavailable error in field Host name1" why does godaddy reject example.com as my DNS server? (they don't accept IP address - saying "Nameserver 1 has an invalid TLD") must i have a NS record for example.com?
Is your ISPConfig server the authoritative name server for example.com? Every domain must have an NS record.
looks like the authoritative name server for my example.com is my ISP's DNS... i did a: dig sub1.example.com @example.com and i see that sub1.example.com resolves to the correct IP... so what must i do to get things right? (i need to be able to use sub1.example.com)
Do you want ot use sub1.example.com for a web site? If its A record points to the correct (public) IP address, then everything's fine.
yes, that is what i'd like to do... however it is not fine, because i can't ping sub1.example.com and i can't browse http://sub1.example.com maybe i didn't create the host sub1.example.com correctly from ispconfig?
digging it doesn't return me my IP address... in my DNS manager, i have these settings: ================= domain: domain (soa) = example.com options: nameserver1 = example.com nameserver2 = example.com Records: A record ip-addresse = myipaddress hostname = sub1 ================= currently my ISP is the authoritative server for my domain example.com