Coming Soon: GET:IT Endpoint Management 1-Day Conference on September 28th at 9:30 AM ET Coming Soon: GET:IT Endpoint Management 1-Day Conference on September 28th at 9:30 AM ET

I can resolve mu FQDN but not DN

Home Forums Server Operating Systems Windows Server 2016 I can resolve mu FQDN but not DN

Viewing 1 post (of 1 total)
  • Author
    Posts

  • oudmaster
    Member
    #167732

    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 !?

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

Live Webinar: Active Directory Security: What Needs Immediate Priority!Live on Tuesday, October 12th at 1 PM ET

Attacks on Active Directory are at an all-time high. Companies that are not taking heed are being punished, both monetarily and with loss of production.

In this webinar, you will learn:

  • How to prioritize vulnerability management
  • What attackers are leveraging to breach organizations
  • Where Active Directory security needs immediate attention
  • Overall strategy to secure your environment and keep it secured

Sponsored by: