General discussion

Locked

DNS zone naming

By Trudy's Support ·
I have an active directory integrated DNS server on a W2K box. Within my domain, there are 5 DNS servers that act as secondaries of this ADI server. My problem is that when a client tries to browse to our public WWW server by entering http://domain.com, they get one of the 5 name servers (that happen to also be hosting WWW servers for our managers of those locations) I have a record for www.domain.com, and tried to add a CNAME for trudys.com, but since there are glue records created automatically for the Nameservers, can't. So...how do I get my DNS server to resolve domain.com to my public webserver without putting each location into a child domain of domain.com?

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

DNS zone naming

by ptchtech In reply to DNS zone naming

I would not be a bad idea to have your web server in a dmz of domain.com and have your private network in xyz.domain.com for security purposes, but that doesn't answer your question. Your problem is a firewall issue. You need to set up a rulethat directs all incoming port 80 to your web servers IP address. Also how big is your network? 5 active directory integrated DNS servers seems like it may be a bit overkill, adding to the directory services replication. You also may want to consider not having your web servers on your dns servers. But from your question it sounds like your number 1 concern should be to button up your firewall issues. Perhaps having your public webserver hosted by a third party (it's cheap) and closing incomingport 80 completly would be a good idea

Collapse -

DNS zone naming

by Trudy's Support In reply to DNS zone naming

My problem is in fact NOT a firewall issue, as there is no firewall in place.

My public site IS hosted by a third party.

The problem remains pointing users to my Public webpage without explicitly typing www.domain.com. Is there HTML forwarding that could be used? The "manager's" websites need access only from explicitly typing in the manager.domain.com format. Seems easy enough, I just don't know what to do, and am pointing the finger at DNS since it is resolving the site.

Collapse -

DNS zone naming

by ptchtech In reply to DNS zone naming

A simple workaround would be to register another Domain name domain.net or any other name. have your web server host set up your new domain name to be an alias of your existing one. you will bypass any name resolution problems. I know its not what you were looking for, but I'm sure the internal users could get used to domain.net instead of domain.com, and it would cost you probably no more than 20 to 50 bucks per year

Back to Windows Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums