Announcement

Collapse
No announcement yet.

DNS not resolving remote server name

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

  • DNS not resolving remote server name

    I have two servers in p.com.au called Playcorp1 [192.168.10.8] & Playcorp2 [192.168.10.11]. I have one server in s.com.au called Proxima [192.168.20.20].

    When logged onto Proxima, I can ping Playcorp2:
    C:\>ping playcorp2

    Pinging playcorp2.s.com.au [192.168.10.11] with 32 bytes of data:

    Reply from 192.168.10.11: bytes=32 time<1ms TTL=127
    Reply from 192.168.10.11: bytes=32 time<1ms TTL=127
    Reply from 192.168.10.11: bytes=32 time<1ms TTL=127
    Reply from 192.168.10.11: bytes=32 time=1ms TTL=127

    Ping statistics for 192.168.10.11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

    C:\>
    I can not, however, ping Playcorp1:
    C:\>ping playcorp1
    Ping request could not find host playcorp1. Please check the name and try again.


    C:\>
    I can, tho, ping Playcorp1 if I use its FQDN:
    C:\>ping playcorp1.p.com.au

    Pinging playcorp1.p.com.au [192.168.10.8] with 32 bytes of data:

    Reply from 192.168.10.8: bytes=32 time<1ms TTL=127
    Reply from 192.168.10.8: bytes=32 time=5ms TTL=127
    Reply from 192.168.10.8: bytes=32 time=1ms TTL=127
    Reply from 192.168.10.8: bytes=32 time<1ms TTL=127

    Ping statistics for 192.168.10.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 5ms, Average = 1ms

    C:\>
    I've checked the DNS server on Proxima, and under DNS\PROXIMA\Forward Lookup Zones\p.com.au, it shows entries for both Playcorp servers:

    playcorp1, Host(A), 192.168.10.8
    playcorp2, Host(A), 192.168.10.11

    Here is the IPCONFIG for Proxima:
    C:\>ipconfig/all

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : PROXIMA
    Primary Dns Suffix . . . . . . . : sundays.com.au
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : sundays.com.au
    com.au

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
    Physical Address. . . . . . . . . : 00-02-55-D6-C4-60
    DHCP Enabled. . . . . . . . . . . : No
    IP Address. . . . . . . . . . . . : 192.168.20.20
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.20.1
    DNS Servers . . . . . . . . . . . : 192.168.20.20
    193.1.1.101
    Primary WINS Server . . . . . . . : 192.168.20.20
    Secondary WINS Server . . . . . . : 193.1.1.101

    C:\>
    Note: 193.1.1.101 is a domain controller running DNS & WINS.

    Can someone see what the issue is?
    |
    +-- JDMils
    |
    +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
    |

  • #2
    Re: DNS not resolving remote server name

    The responce your getting back from playcorp2 is as if it were in the s.com.au domain when it should be in the p.com.au domain. Check your DNS server for s.com.au and see if you have a A host record for playcorp2.s.com.au

    The responce your getting back from playcorp1 would be correct as, by default, your trying to ping <host>.s.com.au as this will be the DNS suffix for the domain. It can't find a host for playcorp1.s.com.au but since you use the FQDN it either uses recursion or you may have forwarders or stud zones to point you to a DNS server in the p.com.au

    I understand this may sound a bit confusing but what are you trying to achieve? Do you want to be able to ping hosts in the p.com.au domain from s.com.au?

    Michael
    Michael Armstrong
    www.m80arm.co.uk
    MCITP: EA, MCTS, MCSE 2003, MCSA 2003: Messaging, CCA, VCP 3.5, 4, 5, VCAP5-DCD, VCAP5-DCA, ITIL, MCP, PGP Certified Technician

    ** Remember to give credit where credit is due and leave reputation points sigpic where appropriate **

    Comment


    • #3
      Re: DNS not resolving remote server name

      I've checked the DNS server in s.com.au for an A record for the server Playcorp2 and there is none. So somehow the Proxima server, in the s.com.au domain (this is an internal AD domain, not on the internet) is finding it somwhere. Here's the NSLookup in the s.com.au domain:
      C:\>nslookup
      Default Server: proxima.s.com.au
      Address: 192.168.20.20

      > set type=ns
      > proxima
      Server: proxima.s.com.au
      Address: 192.168.20.20

      s.com.au
      primary name server = proxima.s.com.au
      responsible mail addr = hostmaster.s.com.au
      serial = 183
      refresh = 900 (15 mins)
      retry = 600 (10 mins)
      expire = 86400 (1 day)
      default TTL = 900 (15 mins)
      > playcorp2
      Server: proxima.s.com.au
      Address: 192.168.20.20

      s.com.au
      primary name server = proxima.s.com.au
      responsible mail addr = hostmaster.s.com.au
      serial = 183
      refresh = 900 (15 mins)
      retry = 600 (10 mins)
      expire = 86400 (1 day)
      default TTL = 900 (15 mins)
      > playcorp1
      Server: proxima.s.com.au
      Address: 192.168.20.20

      s.com.au
      primary name server = proxima.s.com.au
      responsible mail addr = hostmaster.s.com.au
      serial = 183
      refresh = 900 (15 mins)
      retry = 600 (10 mins)
      expire = 86400 (1 day)
      default TTL = 900 (15 mins)
      > ?
      Here's some more infor which might help you to help me:
      > set type=a
      > playcorp2
      Server: proxima.s.com.au
      Address: 192.168.20.20

      Name: playcorp2.s.com.au
      Address: 192.168.10.11

      > playcorp1
      Server: proxima.s.com.au
      Address: 192.168.20.20

      *** proxima.s.com.au can't find playcorp1: Non-existent domain
      > p.com.au
      Server: proxima.s.com.au
      Address: 192.168.20.20

      Name: p.com.au
      Addresses: 192.168.10.8, 192.168.10.11

      > set debug
      > playcorp1
      Server: proxima.s.com.au
      Address: 192.168.20.20

      ------------
      Got answer:
      HEADER:
      opcode = QUERY, id = 14, rcode = NXDOMAIN
      header flags: response, auth. answer, want recursion, recursion avail.
      questions = 1, answers = 0, authority records = 1, additional = 0

      QUESTIONS:
      playcorp1.s.com.au, type = ANY, class = IN
      AUTHORITY RECORDS:
      -> s.com.au
      ttl = 3600 (1 hour)
      primary name server = proxima.s.com.au
      responsible mail addr = hostmaster.s.com.au
      serial = 183
      refresh = 900 (15 mins)
      retry = 600 (10 mins)
      expire = 86400 (1 day)
      default TTL = 900 (15 mins)

      ------------
      ------------
      Got answer:
      HEADER:
      opcode = QUERY, id = 15, rcode = NXDOMAIN
      header flags: response, auth. answer
      questions = 1, answers = 0, authority records = 1, additional = 0

      QUESTIONS:
      playcorp1.com.au, type = ANY, class = IN
      AUTHORITY RECORDS:
      -> com.au
      ttl = 86400 (1 day)
      primary name server = ns1.ausregistry.net
      responsible mail addr = dns.ausregistry.net.au
      serial = 2010546066
      refresh = 14400 (4 hours)
      retry = 3600 (1 hour)
      expire = 3600000 (41 days 16 hours)
      default TTL = 86400 (1 day)

      ------------
      *** proxima.s.com.au can't find playcorp1: Non-existent domain
      >
      I'm looking in Replmon on Proxima and it is replicating with Playcorp2 and not Playcorp1. What's going on?
      Last edited by JDMils; 6th July 2007, 00:30.
      |
      +-- JDMils
      |
      +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
      |

      Comment


      • #4
        Re: DNS not resolving remote server name

        Here's something......

        I added the p.com.au domain to TCP/IP\Advanced\DNS\Append these DNS suffixes (in order) to the Proxima server's Local Area Connection. Now, when I do an IPCONFIG, I get:
        C:\>ipconfig /all

        Windows IP Configuration

        Host Name . . . . . . . . . . . . : PROXIMA
        Primary Dns Suffix . . . . . . . : s.com.au
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : s.com.au
        v.com.au
        p.com.au

        Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix . :
        Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
        Physical Address. . . . . . . . . : 00-02-55-D6-C4-60
        DHCP Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.20.20
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.20.1
        DNS Servers . . . . . . . . . . . : 192.168.20.20
        193.1.1.101
        Primary WINS Server . . . . . . . : 192.168.20.20
        Secondary WINS Server . . . . . . : 193.1.1.101

        C:\>
        Now when I ping the Playcorp1 & Playcorp2 servers from Proxima, I get:
        C:\>ping playcorp1

        Pinging playcorp1.p.com.au [192.168.10.8] with 32 bytes of data:

        Reply from 192.168.10.8: bytes=32 time<1ms TTL=127
        Reply from 192.168.10.8: bytes=32 time<1ms TTL=127
        Reply from 192.168.10.8: bytes=32 time<1ms TTL=127
        Reply from 192.168.10.8: bytes=32 time<1ms TTL=127

        Ping statistics for 192.168.10.8:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
        Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

        C:\>ping playcorp2

        Pinging playcorp2.s.com.au [192.168.10.11] with 32 bytes of data:

        Reply from 192.168.10.11: bytes=32 time<1ms TTL=127
        Reply from 192.168.10.11: bytes=32 time<1ms TTL=127
        Reply from 192.168.10.11: bytes=32 time<1ms TTL=127
        Reply from 192.168.10.11: bytes=32 time<1ms TTL=127

        Ping statistics for 192.168.10.11:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
        Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

        C:\>
        So now I can ping Playcorp1 But I still don't understand why the different domain suffixes appear for two servers in the same domain, p.com.au?? They are ONLY listed in the p.com.au Forward Lookup Zones in DNS.
        |
        +-- JDMils
        |
        +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
        |

        Comment

        Working...
        X