I can resolve mu FQDN but not DN Share on Facebook Tweet on Twitter Share on LinkedIn Home › Forums › Server Operating Systems › Windows Server 2016 › I can resolve mu FQDN but not DN This topic contains 3 replies, has 3 voices, and was last updated by wullieb1 1 month, 2 weeks ago. Viewing 4 posts - 1 through 4 (of 4 total) Author Posts oudmasterMember September 30, 2018 at 11:31 am #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 !? OssianModerator October 1, 2018 at 2:28 am #192137 Are the domain suffixes set correctly? OssianModerator October 1, 2018 at 10:32 am #192138 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 wullieb1Participant October 5, 2018 at 4:16 am #245832 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 Author Posts Viewing 4 posts - 1 through 4 (of 4 total) You must be logged in to reply to this topic.