1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Wee DNS error

Discussion in 'Networks' started by Stoney, May 4, 2007.

  1. Stoney

    Stoney Megabyte Poster

    731
    23
    69
    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.
     
    Certifications: 25 + 50 metre front crawl
    WIP: MCSA - Exam 70-270
  2. r.h.lee

    r.h.lee Gigabyte Poster

    1,011
    52
    105
    Stoney,

    Do you have a router between the 192.168.1.0 subnetwork nad the 192.168.2.0 subnetwork?
     
    Certifications: MCSE, MCP+I, MCP, CCNA, A+
    WIP: CCDA
  3. Stoney

    Stoney Megabyte Poster

    731
    23
    69
    Yes, there is a router on the edge of each subnet.
     
    Certifications: 25 + 50 metre front crawl
    WIP: MCSA - Exam 70-270
  4. Vendetta

    Vendetta Nibble Poster

    56
    0
    9
    is this an AD domain ? if it is are the ws joined to the domain?
     
  5. r.h.lee

    r.h.lee Gigabyte Poster

    1,011
    52
    105
    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?
     
    Certifications: MCSE, MCP+I, MCP, CCNA, A+
    WIP: CCDA
  6. Bluerinse
    Honorary Member

    Bluerinse Exabyte Poster

    8,871
    167
    256
    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?
     
    Certifications: C&G Electronics - MCSA (W2K) MCSE (W2K)
  7. Tartanbill

    Tartanbill Bit Poster

    31
    2
    3
    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.
     

Share This Page

Loading...