IT Employment

Ask something
Discussion Locked

Configuring multiple DNS Domain names

0 helpful
4 replies

by stnkmstr 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm trying to configure our Win2k workstations for multiple DNS domain names. Normally we've been doing this manually for every workstation on the floor that needs the configuration through the DNS tab in the Advanced TCP/IP settings property page. However, now my boss wants to roll this thing out company wide. I thought that I could configure this setting in the DHCP scope options, but unfortunately the only scope option that came close was 015, and you can only configure the primary DNS suffix in that option. I need to enter 3 DNS suffixes. Does anybody know a way that I can automatically configure these settings domain wide or am I stuck configuring these suffixes manually at each workstation. Any suggestions would be greatly appreciated.

4 replies

by lordinfidel

Not really understanding the need for multiple DNS names on wkstns?

Any particular reason why.

I'm not being a dick, I am just curious as to why.

by stnkmstr

We have 3 forests with different DNS names. Our primary domain hosts secondary DNS zones for the two other forests. We want to be able to resolve these names in a URL from the primary domain for web purposes. So for example, we want to enter http://testmachine/wwwroot in a browser from a production machine in the primary domain where "testmachine" is actually in a different DNS zone then the primary DNS zone. Entering this URL on our production machines from the primary domain will work, only if the DNS name is configured in the search list on the local machine. I found that there actually is a way to configure up to 2 using the DHCP scope option 015, but to configure 3, it looks like I'm stuck doing it manually, or using some kind ofscript to get the job done. I know it sounds a little confusing, but I hope this helps clarify the issue a little better....an don't worry. I didn't think you were a dick

by lordinfidel

when you put in http://testmachine/wwwroot

was testmachine a fqdn? If not that could be the issue. Remember how AD works in regards to DNS.

The reason it works with the search order is that when it resolves it will look in that search order for the name and then resolve it to a fqdn then to IP.

To see this in it's glory. Open a command prompt and ping a machine name that belongs to the same domain you are in.

See what it comes back with. It should come back with a fqdn name, notjust the machine name, even though you only typed in the machine name.

But if you type in a machine that does not belong to that domain, it will not know where to look.
(and too my knowledge there is not way to set up in the dhcp scope extra domain names)

by tmills

I feel better knowing that I am not the only person with the same question. DHCP scopes should pass out all the information you need it to. I have been trying to figure this one out for a while. I have several domains and really do not feel like hitting every workstation. If we aren't the only ones thinking this way, you would think that MS would have thought of it as well unless they have some logical reason and have not shared it.

This discussion is closed to new replies.