Add windows-specific dns guidance to beginner tutorials

[dncnkrs]

Please search the existing issues for relevant feature requests, and use the reaction feature (https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to add upvotes to pre-existing requests.

Feature Description

The Consul beginner tutorials demonstrate queries against Consul's DNS server. The documentation is heavily geared towards unix systems, but could easily be adapted to include windows users.

The two issues I found were:

• 'dig' is not used on Windows. Instead, we use nslookup or (in powershell) Resolve-DnsName.
• I'm not sure of the mechanism behind this, but I couldn't find a way to query Consul DNS on port 8600. I solved this by binding to port 53 in a config file. The problem I see hear is pedagogical - in the tutorial series, config files aren't explained until the tutorial after DNS lookups are introduced. I appreciate very few people will be installing consul without at least knowing what DNS is and how config files work, but it could be a source of frustration.

I think windows users (who often don't choose to be using windows, mind) would benefit from a small box explaining this windows-specific configuration. At least, a pointer to the configuration docs page and the relevent docs for the cmd and PS utilities could speed this process up.

Use Case(s)

New windows users learning consul.

[idrennanvmware]

We actually haven't gotten DNS working on windows for this reason - do you happen to have the config and steps you used? Would love to reference it (we have a mix of linux using DNS and windows not using DNS)

[dncnkrs]

We actually haven't gotten DNS working on windows for this reason - do you happen to have the config and steps you used? Would love to reference it (we have a mix of linux using DNS and windows not using DNS)

You have me worried - have I done something inadvisable?!?!

A few exisiting issues pointed to Window's difficulty with DNS servers that aren't running on port 53. So I figured I needed to run DNS on port 53. I didn't run into any administrator issues.

Add this section to the top-level config file:

// consul.json
"ports": {
	"dns": 53
},

Then, from PowerShell: Resolve-DnsName -Name "nodename.node.consul" -Server hostname

[idrennanvmware]

We can give it a try. This doesn't hijack all DNS? I'm surprised administrator permission isn't required but I won't complain lol

I'm not the best with Networking, so I would not base worry on my implementations around it 😂😂