Announcement

Collapse
No announcement yet.

I can resolve mu FQDN but not DN

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

  • I can resolve mu FQDN but not DN

    Hi,

    I created new AD, and DNS is also installed,

    I cant resolve the domain name, but I can resolve the FQDN !!?


    Sample:


    > mo****
    Server: localhost
    Address: 127.0.0.1

    *** localhost can't find mo****: Non-existent domain

    > mo****.local
    Server: localhost
    Address: 127.0.0.1

    Name: mo****.local
    Addresses: 192.168.1.30
    192.168.1.31

    >



    how can I solve it !?

  • #2
    Are the domain suffixes set correctly?
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

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

    Comment


    • #3

      Do you mean under UPN Suffix ?

      if yes, I have already added it, please see the attachment
      Attached Files

      Comment


      • #4
        No - in DNS settings on the LAN connection (or via the DHCP server), you can specify domain suffixes which will be appended to single name DNS queries
        Tom Jones
        MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
        PhD, MSc, FIAP, MIITT
        IT Trainer / Consultant
        Ossian Ltd
        Scotland

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

        Comment


        • #5
          DN as is DistinguishedName or the NetBIOS name?

          From what it looks like to me your trying to resolve the m*** name as opposed to m****.local

          m*** is your netBIOS name which is typically WINS
          m***.local is your FQDN which is DNS

          Comment

          Working...
          X