Search results for query: *

Great support/advice from everyone. I really appreciate the wisdom. Let me mull over some of this and revisit the thread tomorrow. Again much appreciated, -marc

Thanks Cory, not sure I wanted to hear that, but... How about this: Would it be useful/work if I could get the campus bind/dns system to send me zone transfers? like all the 10.10.11.0 entries to the w2k3/DNS system? Perhaps that way, the w2k3 DNS could stay current? regards, -marc

thank you lhuegele, That's the first thing I tried but it does not seem to work as I understand it. Go to the forwarders tab, under "All other DNS domains" add the campus bind/DNS system right? I'm thinking the trouble may be that w2k3/DNS is forwarding a domain lookup that "it" thinks it is...

The trouble I’m having/understanding quite simply is that there are other (non MS) Systems on one or two of these domains that will never have anything to Do with the AD/DNS/w2k3 systems. Coincidentally, they are in the same Domain and share the same IP ranges. It’s the XP clients that need...

Cory, > Ok so you pretty much have the idea to have both dns >servers accepting dynamic updates and replicating >changes between these systems. No, I have no control over the campus bind DNS and it does not and probably never will support dynamic updates. New users must manually register their...

itsp1965, The bind DNS system is totally out of my control and serves the entire campus. Are you saying that the AD/DNS system can be configured on the w2k3 server to be secondary. Initial queries from clients will be sent to bind/DNS first, then to AD/DNS? Thanks, -marc

Cory, thanks for the darn fast response! The issue with creating entries in the w2k3 DNS for these “other” IP names in the IP domain, is that they get their IP numbers via DHCP and there is no guarantee they will always be the same. Additionally, each time a campus (bind) entry is added...

Hopefully someone can help me understand the interaction of DNS resolution between 2003 servers and XP clients. I understand that in AD it’s probably best to have the clients (XP) use the DNS server running in the AD domain. And many things seem to work better when it is setup like this...

You guys are great! Thanks for the speedy responses. I know this sounds like the correct thing to do. And that would be fine if Microsoft products were the only thing in the universe, however, it’s not a very practical solution. Besides, I like the idea of not having to fuss with IP and DNS...

Thanks RoadKi11. I’ve tried that but am a bit confused about the difference between NetBIOS names and IP names and how these things are resolved. The domain name the XP clients want to join is called win-dom while the IP name of the server is a.b.c.edu. I’ve tried adding an alias of win-dom...

Migrating from NT 4.0 to Win 2003 R2 I have used the following steps. However, I seem to have a "lack of understanding" of the DNS system on W2k3 and XP. After the migration steps are finished, the XP system can not join the pre-existing domain. DNS does not resolve the domain name from the DNS...