What problem are you having?
|
Cause: This error occurs if DNS zone file is corrupt. Solution: Host should check the event log and remove any zone file errors reported there. Restart of DNS server may help.
|
|
Cause: It occurs if the DNS zone file is not found at the target location. Solution: Host should check for the zone file existence in the DNS server root path. e.g. for MS DNS root path (by default) is C:\winnt\system32\dns .
|
|
Cause: It occurs if DNS root path is invalid. Solution: Host should check the path of DNS server in HC settings.
|
|
Cause: It occurs if HC is unable to save changes made in the DNS zone file. Solution: Host should check the path of DNS server in HC settings and permissions on the DNS root folder.
|
|
Cause: This happens if HC is not configured properly. Solution: To solve this problem, see the following check points.
DNS is on remote machine, HC is creating zone file but domain is not accessible |
Cause: If you are using MS DNS and DNS server is configured to load zones from File instead of load zone from Registry or Active Directory and Registry. Reason being that HC supports only registry DNS.
Solution: Change the load zone data on startup option in DNS server to From Active Directory or registry.
To change zone loading:
Open DNS.
On the Action menu, click Properties.
On the Advanced tab, note the Load zone data onstartup and change it to From Active Directory andregistry, click Ok.
Notes:To open DNS, click Start, point to Programs, point to Administrative Tools, and then click DNS.
If reseller encounter above errors, he should contact his host administrator. If your problem still persist, please contact us.