Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • Your answers seem to have a blend of what is happening. Option 1 - this works reliably on the same subnet. However the solution required uses the *.ns.exampledomain.com part to force IP address resolution at the DNS/domain controller in order to cross subnets eliminating the switch problem whilst not relying on a volatile IP address. Option 2 - in the screenshot provided, the "DNS Suffix for this connection" is "ns.exampledomain.com" and "Use this connection's DNS suffix in DNS registration" is checked. This configuration is what I am trying to replicate on the RPi. Commented Jun 10, 2016 at 20:23
  • The reason this ended up being chose as the answer is in part due to the server side settings mentioned at the start. It turns out that on the network, there existed a 'public' DNS manager for ns.exampledomain.com that was used for most DNS purposes including Windows clients who were configured to use it. There was also another hidden manager that was responsible for a hidden otherns.exampledomain.com that is used with clients on Mac/Unix/etc to handle their form of DNS requests. Commented Jun 15, 2016 at 15:08