The DNS server is running perfectly now. I do have a simple problem. I have another server running on the network. It is just running windows xp pro and is being used as a security server for a survanlence system. The survanlance system has its own buildt in web server that allows remote access. Right now, that server is running on port 79. So for remote access I go to: 65.40.8.203:79. I am trying to make it where I don't have to type the IP address. Just type, security.uptechusa.net and it take me to the server. I had this set-up like this before when I was using godaddy's DNS. I have created a CNAME security that is forwarding to but does not seem to work correctly. Any ideas?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
DNS CNAME help
- Thread starter djpic
- Start date
First of all, DO NOT list public IP's and names with a port forwarder on the web. This is insecure and you are opening the door to the unethical ones...just a friendly tip.
Now for your question:
Task 1:Go through each CNAME entry, and make sure that the CNAME entry resolves correctly to an IP address. For example, if you have "xxx.example.net CNAME xxx.myisp.net", make sure that "xxx.myisp.net" has an A record pointing to a valid IP address. Also, make sure that the IP address responds as expected (in this case, run a program to connect to the server).
Task 2:Make sure that you have no unnecessary CNAME entries; they can make things confusing, and are only recommended if you have a legitimate need to have them and are quite familiar with DNS.
Task 3: If you have a CNAME entry, make sure that it is the ONLY resource record for that domain. For example, if you have " CNAME lab.example.net", you must not have any A records, MX records, etc. for "
Task 4:You must not have an NS record pointing to a CNAME. For example, "example.net NS dns.example.net" and "dns.example.net CNAME ns0.example.net" this will cause problems.
Hope you find this helpful
George
Now for your question:
Task 1:Go through each CNAME entry, and make sure that the CNAME entry resolves correctly to an IP address. For example, if you have "xxx.example.net CNAME xxx.myisp.net", make sure that "xxx.myisp.net" has an A record pointing to a valid IP address. Also, make sure that the IP address responds as expected (in this case, run a program to connect to the server).
Task 2:Make sure that you have no unnecessary CNAME entries; they can make things confusing, and are only recommended if you have a legitimate need to have them and are quite familiar with DNS.
Task 3: If you have a CNAME entry, make sure that it is the ONLY resource record for that domain. For example, if you have " CNAME lab.example.net", you must not have any A records, MX records, etc. for "
Task 4:You must not have an NS record pointing to a CNAME. For example, "example.net NS dns.example.net" and "dns.example.net CNAME ns0.example.net" this will cause problems.
Hope you find this helpful
George
- Thread starter
- #3
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question