JohnGrime/ZeroconfScan: DNS.go; 3 LoC

Found a possible issue in [JohnGrime/ZeroconfScan](https://www.github.com/JohnGrime/ZeroconfScan) at [DNS.go](https://github.com/JohnGrime/ZeroconfScan/blob/fb8eabbc24cef4ca6a660b38d16fe32b8ff8e1d9/DNS.go#L413-L415)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

>

[Click here to see the code in its original context.](https://github.com/JohnGrime/ZeroconfScan/blob/fb8eabbc24cef4ca6a660b38d16fe32b8ff8e1d9/DNS.go#L413-L415)

Click here to show the 3 line(s) of Go which triggered the analyzer.

```go
for _,rr := range(m.Answer) {
rr_print(indentx2, &rr)
}

```

Click here to show extra information the analyzer produced.

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {rr_print 2} was not found in the callgraph; reference was passed directly to third-party code
```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: fb8eabbc24cef4ca6a660b38d16fe32b8ff8e1d9

Start with DNS.go lines 413-415 and inspect the rr_print call in its surrounding context. Check whether passing &rr from the range loop creates the reported issue, then classify the finding by leaving the appropriate reaction on the issue.

Written by the indexing model from the issue text.