DNS Server (same as parent folder) issue 1

[cooperchien]

I have an Active Directory network which has the domain name of abc.net. I also 2 DNS servers which have the ip of 10.0.0.1 and 10.0.0.2. My web server's ip is 10.0.0.3.
My users would like to enter abc.net on their browsers to enter the company website.
Therefore, I set a host record of 10.0.0.3 on (same as parent folder) in DNS servers.
However, for some reasons, my 2 DNS servers keep registering 10.0.0.1 and 10.0.0.2 on (same as parent folder) record.
As a result, when my users type abc.net, their browsers direct them to 10.0.0.1 or 10.0.0.2 first instead of the wbesite server's ip.
I deleted the 10.0.0.1 and 10.0.0.2 record on (same as parent folder) but they come back next morning. Is there something I am missing here? Please help.
The goal is to let my users to access the company website by entering only abc.net which happens to be the same as the Active Directory domain name.
Thanks in advance.

 

[PScottC]

The records that you tried to delete are required for AD to function properly. Why not simply create an alias record called "intranet" and point that record to your webserver?

Your other option would be to install IIS on your DC's and set them to redirect all hits to another server. (I don't really recommend this because it exposes your DC's to more security risks)

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[cooperchien]

That is really too bad. So out of all 3 host records of (same as parent folder), the ping request or web traffic request to abc.net will always go to 10.0.0.1 first. If I change the ip address of my webserver to 10.0.0.1, will that solve the problem? I assume that the DNS server will chose because the ip address number is smaller, the DNS server will point to 10.0.0.1 instead of 10.0.0.3, right?

 

[PScottC]

No... DNS will "round-robin" the request and you will get wierd results. Some clients will connect and others won't.

I strongly recommend having your users type "intranet" to get the site. You don't need to provide a full qualified domain name (ie... abc.net extension not required).

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[cooperchien]

Thank you for your tip. I am going to use just intranet. By the way, I post a question but no one answered. Do you know if MS DNS has wildcard settings like "*"?

 

[PScottC]

Not that I am aware of. I've never used it or seen it used. Is it an option of BIND?

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[cooperchien]

I used this option in other DNS service providors such as godaddy.com. I also heard that Linux DNS can use wildcard.
My other post on this issue had no reponse and no answer I could find from Microsoft.com, too. I guess MS DNS does not have this feature.