• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 2000 DNS problem

Y

y2kc

Platinum Member
This should be simple for some of you guys so here goes...

I've split my home-lan into two segments (for learning purposes)

Segment 1: 10.0.x.x subnet: 255.255.0.0
Segment 2:10.1.x.x subnet :255.255.0.0

1. My Domain Controller (10.0.0.100) is also my DNS server for the lan (using my ISPs DNS servers as forwarders).
2. Name resolution is taking place on the 10.0.x.x segment.
3. The segments are connected through a cisco 1605r router.
4. I can ping all of the machines from one segment to the other by IP.
5. I can ping by name from the e1 interface (10.1.0.1) which is the gateway for my 10.1.x.x segment but I cannot ping by name from the clients on that side (by IP, I can ping and browse the net) .
6. If I enter my ISPs DNS servers into the tcp/ip properties of my clients on the 10.1.x.x segment, name resolution takes place to the internet but obviously not to the 10.0.x.x segment of my lan.
7. The two machines on the 10.1.x.x segment cannot join the domain until I solve this problem.

There is no firewall between the segments nor on the client machines. There is a problem with how the DNS server is set up, I just dont have any idea as to what it migh t be.

edit: I'm going to try to create a HOST file but I'd like to know how to do without it if possible.

Any help would be greatly appreciated.
 
To restate your problem, the clients on the 10.1 subnet are unable to resolve names, when their DNS server is on the 10.0 subnet?

I know the cabling is ok, since you can ping by address.
I think the (client-side) gateway is ok, since you can ping by address.
I wonder, can the DNS server ping the clients by address?
Is the server-side gateway correctly configured?
Does the router have a route defined from the server-side (10.1) to the client-side (10.0)?

I'm wondering if the clients are working fine, but the DNS server can't respond to requests, because of some sort of routing problem. (gateway setting or router).
 
Are the Addresses being assigned by DHCP?
Are you using Dynamic DNS?
Is it a Windows 2000 Server?
Do you have a DNS zone on your server for the 10.1.0.0 subnet?

By default, the DNS server only provides name resolution for its own subnet. You'll probably need to open the DNS Snap-in and create a forward lookup zone for the second subnet. That said, if the answers to any of the first three questions are no, you may have to do something different.
 
I'm wondering if the clients are working fine, but the DNS server can't respond to requests, because of some sort of routing problem. (gateway setting or router).
Click to expand...

Woodie you seem to have hit the nail on the head here. My DNS (Win 2000) server's gateway was (is) pointing to my Firewalls private interface. I added my routers IP address (10.0.0.1) as a gateway and I was able to browse by name. I did a nslookup and my server was recognized as the dns server.....and until I switched things back around to test the configuration, everything worked perfectly. that's when things got weird.

I won't bore you with the details but thanks for pointing me in the right direction.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top