Wee DNS error

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hi,

Just setting up my lab and I don't think I have DNS set up correctly.

I have 2 subnets 192.168.1.xxx and 192.168.2.xxx. The DNS server is subnet 192.168.2.

I have configured a Forward Lookup zone that contains A records from both subnets. However, I can only resolve DNS queries from the subnet the DNS server is on.

I currently have 2 forward look up zones, local and mydomain.local.

All entries are in mydomain.local.

PC's on subnet 192.168.1 get the correct DNS server in nslookup but it fails to resolve any names.

Can anyone suggest what the problem may be?

Thanks.

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Stoney,

Do you have a router between the 192.168.1.0 subnetwork nad the 192.168.2.0 subnetwork?

 

Yes, there is a router on the edge of each subnet.

 

is this an AD domain ? if it is are the ws joined to the domain?

 

Stoney,

Questions:

1. Can you ping from a 192.168.1.0 host to the IP address of the DNS server in the 192.168.2.0 network?
2. Can you ping from a 192.168.2.0 host to the IP address of the DNS server?

 

Yes it sounds more like a routing issue, meaning that packets sent to the 192.168.2.0 subnet from the 192.168.1.x hosts may not be getting there and vice versa.

What device are you using as a router?

 

Highliy indicative of a routing issue as these are different subnets.

You say you have a router; what is it and how is it configured?

If you want to know for sure that it's a routing problem then do a traceroute from a host in one subnet to a host in another and if it doesn't cross into the other subnet, you know you have a routing issue.