Announcement

Collapse
No announcement yet.

DNS, NSLookup problem

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • DNS, NSLookup problem

    Configuration:
    Windows 7 machine and windows 2003 machine connected through a router, windows 2003 also connected to the internet modem. Windows 2003 handels the internet connection.

    Windows 2003 has 2 nics, one connected to the internet modem, the other to the internal network.

    When I perform nslookup it returns with the internet modem and the ip address of that modem. That's not what I want. It should return windows 2003 machine and not the modem.
    The internet modem is not registered in DNS, only the 2003 machine. How can I fix this?

    Greetings

  • #2
    Re: DNS, NSLookup problem

    On the Windows 7 client what have you got configured as primary DNS?
    Can you also post a Ipconfig /all for your win7 machine and the server?

    Ta
    Caesar's cipher - 3

    ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

    SFX JNRS FC U6 MNGR

    Comment


    • #3
      Re: DNS, NSLookup problem

      In this configuration windows 7 is not able to connect to the internet, but it can connect to the server. Windows 2003 can connect to the internet.

      As primary dns: ip of server

      Windows 7:

      Windows IP Configuration

      Host Name . . . . . . . . . . . . : PC2
      Primary Dns Suffix . . . . . . . : test.com
      Node Type . . . . . . . . . . . . : Mixed
      IP Routing Enabled. . . . . . . . : No
      WINS Proxy Enabled. . . . . . . . : No
      DNS Suffix Search List. . . . . . : test.com

      Ethernet adapter Test:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Atheros AR8121/AR8113/AR8114 PCI-E Ethern
      et Controller
      Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
      DHCP Enabled. . . . . . . . . . . : Yes
      Autoconfiguration Enabled . . . . : Yes
      IPv4 Address. . . . . . . . . . . : 192.168.1.11(Preferred)
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Lease Obtained. . . . . . . . . . : dinsdag 8 december 2009 15:38:05
      Lease Expires . . . . . . . . . . : woensdag 16 december 2009 15:57:40
      Default Gateway . . . . . . . . . : 192.168.1.1
      DHCP Server . . . . . . . . . . . : 192.168.1.10
      DNS Servers . . . . . . . . . . . : 192.168.1.10
      NetBIOS over Tcpip. . . . . . . . : Enabled

      Tunnel adapter Teredo Tunneling Pseudo-Interface:

      Media State . . . . . . . . . . . : Media disconnected
      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
      Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes

      Tunnel adapter isatap.mshome.net:

      Media State . . . . . . . . . . . : Media disconnected
      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
      Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes


      Windows 2003:

      Ethernet adapter Internet:

      Connection-specific DNS Suffix . : fritz.box
      IP Address. . . . . . . . . . . . : 192.168.178.22
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Default Gateway . . . . . . . . . : 192.168.178.1

      Ethernet adapter Test:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Realtek RTL8169 Gigabit Ethernet Adapter
      Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
      DHCP Enabled. . . . . . . . . . . : No
      IP Address. . . . . . . . . . . . : 192.168.1.10
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Default Gateway . . . . . . . . . : 192.168.1.1
      DNS Servers . . . . . . . . . . . : 192.168.1.10
      Last edited by Satori; 8th December 2009, 16:22.

      Comment


      • #4
        Re: DNS, NSLookup problem

        Nslookup returns:

        Default Server: fritz.box
        Address: 192.168.178.1

        Comment


        • #5
          Re: DNS, NSLookup problem

          A couple of things I can see from there.

          I take it your Windows 2003 is the Domain Controller. The domain is called Test.com. Is that a correct assumption? If so You'll need to change it as this is a valid, registered TLD. Use another tld intended for internal LAN use such as .local
          Can you specify what type of Modem you are using?
          Based on that you may need to change the network config slightly. It should be like so:
          Physically connect all the devices to the Router/switch then to the modem (Some products have got them all in one)
          Disable the second NIC on the Server (Currently has got an IPIPA address)
          Configure the DNS on the 2003 box to forward internet queries to the Routing Device/ISP or use Root hints whichever is more convenient.
          Caesar's cipher - 3

          ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

          SFX JNRS FC U6 MNGR

          Comment


          • #6
            Re: DNS, NSLookup problem

            Originally posted by Satori View Post
            Nslookup returns:

            Default Server: fritz.box
            Address: 192.168.178.1
            What is Fritz.box? Is that your domain name? What is the PTR record for your DNS server?
            Caesar's cipher - 3

            ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

            SFX JNRS FC U6 MNGR

            Comment


            • #7
              Re: DNS, NSLookup problem

              I've changed the name of the domain for privacy reasons.
              Fritz box is the name of the internet cable modem.
              Ptr: 192.168.1.11 ton2.test.com
              192.168.1.10 ton1.test.com

              Comment


              • #8
                Re: DNS, NSLookup problem

                If I disable the second NIC nslookup returns the correct data:
                Default Server: ton1.test.com
                Address: 192.168.1.10
                The same result I get on the windows 7 machine

                I entered the ISP forwarders in DNS.

                If I ping windows 2003 on windows 7 it returns the correct data:

                Pinging ton1.test.com [192.168.1.10] with 32 bytes of data:

                Reply from 192.168.1.10: bytes=32 time<1ms TTL=128
                Reply from 192.168.1.10: bytes=32 time<1ms TTL=128
                Reply from 192.168.1.10: bytes=32 time<1ms TTL=128
                Reply from 192.168.1.10: bytes=32 time<1ms TTL=128

                But if I do the same on the server it returns the ip address of the server as it is registered in the in the internet modem:

                Pinging ton1.test.com [192.168.178.22] with 32 bytes of data:

                Reply from 192.168.178.22: bytes=32 time<1ms TTL=128
                Reply from 192.168.178.22: bytes=32 time<1ms TTL=128
                Reply from 192.168.178.22: bytes=32 time<1ms TTL=128
                Reply from 192.168.178.22: bytes=32 time<1ms TTL=128
                Last edited by Satori; 8th December 2009, 17:57.

                Comment

                Working...
                X