suffix
2 TopicsDNS for local SOHO, ip ranges and suffixes
Setting up a local DNS on 2019 to eventually become a small AD. IP range used is 192.168.1.1/24 and the number of devices are about 40, including phones and infrastructure and such. I have been reviewing some documentation, but it does not really answer some questions. Gateway is at *.1.1 Server has currently static IP at *.1.51 Can I use an IP from the used range as DNS server or should I use something completely different? I see different answers and references in regards to what local suffix to use, there is an article on MS Tech net advising against using ".local" as local suffix. What goes?1.6KViews0likes3CommentsDNS suffix is added when using nslookup but not when using ping or browsing
Hi everyone, I am using Windows Server 2016, running DHCP and DNS. I have configured DHCP option 15 to add suffix "abc.de". In the DNS server, I've created a zone called "corp.abc.de" .Entries in that zone should be resolvable only by hostname. In theory, if I want to ping user.corp , this should be resolved as the FQDN user.corp.abc.de . example: Server config: A record: "user" inside the forwarding Lookup zone "corp.abc.de" Client machine: We run the below command that works nslookup user.corp Server: DC.corp.abc.de Address: 10.130.3.254 Name: user.corp.abc.de Address: 10.150.70.11 Then we rung the below command that should also work, but it doesn't. ping user.corp Ping request could not find host user.corp. Please check the name and try again. This however, works on Linux machines, but doesn't work on Windows or MAC. I've tried reinstalling the server (both with DC AD and without). After spending 2 days on this, I'm out of ideas. Any help will be highly appreciated.11KViews0likes1Comment