Cant get pod A records to resolve

Is this supported by kwt ?

dns lookup via kubedns directly :

```
> docker exec -it kind-control-plane2 dig kafka-kafka-0.kafka-kafka-brokers.drivenow-staging-z.svc.cluster.local @10.244.1.2
...
;; QUESTION SECTION:
;kafka-kafka-0.kafka-kafka-brokers.drivenow-staging-z.svc.cluster.local. IN A

;; ANSWER SECTION:
kafka-kafka-0.kafka-kafka-brokers.drivenow-staging-z.svc.cluster.local. 8 IN A 10.244.2.24

;; Query time: 0 msec
;; SERVER: 10.244.1.2#53(10.244.1.2)
...
```

dns lookup via kwt net

```
> dig kafka-kafka-0.kafka-kafka-brokers.drivenow-staging-z.svc.cluster.local
...
;; QUESTION SECTION:
;kafka-kafka-0.kafka-kafka-brokers.drivenow-staging-z.svc.cluster.local. IN A

;; Query time: 10 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
...
```

Start by reproducing the two provided dig commands: the direct kubedns query and the query through kwt net. Compare their DNS paths and determine whether pod A-record resolution is supported by kwt. Done means the support status and the cause of the differing results are established, with an appropriate follow-up identified.

Written by the indexing model from the issue text.