Wednesday, September 29, 2004

DNS in Windows - what I'd like to add

Here's a list of 10 things I'd like to see implemented in Microsoft's DNS server, in no particular order.

1. Some Equivalent of BIND's view feature. Uers with one server who want to both host AD and host Internet web sites could use this feature.

2. EDNS0 client awareness. It would be nice for DNS clients to have the option to use EDNS0 to get larger UDP packets back. This could be controlled by client UI (an additional check box), reg settings, and/or group policy.

3. DIG.exe, as a replacement for nslookup. Nslookup is ok if you know what you are doing, but not much help in diagnoisis.

4. Full support for DNSsec. The tools to create a key and sign a zone or specific resource record and generate NXT records are needed, as is client support for DNSSec.

5. Better DNS and DCHP integration. DHCP servers should replicate their DHCP databases etc, via AD and then to co-ordinate the zones. This would give a better intergration with DNS, and better control over DHCP servers.

6. An additional command in NET.EXE: net restart which would stop then start the respective service (e.g NET RESTART "DNS SERVER" to bounce the server). This should work with ALL NET services!

7. Decent documentation on DNS statistics provided by by dnscmd. There are hundreds of statistics produced - and these are not documented. I'd like to see better documentation on what these are, plus a -v option to only display some of them when really needed (and to limit the number shown by default).

8. English language explanations for DNS errors in AD. I see, all too often, bogus error messages that are _really_ DNS errors. For example, go to DNS, and delete the zone for your AD, then run one of the DNS tools. The error message (for example,RPC failure) might be strictly speaking true, but it's very little use in roubleshooting. I'd like to see better diagnostic messages returned from the MMC tools - and have them consistent. Ideally, these tools should work out that the DNS lookup has failed, do some more testing, then put up a more meaningful and accurate error message!

9. More prescriptive guidance for DNS.

10. DNS MOC course. A 2-3 day course covering all about DNS, including interop with BIND, setup, deployment, DNS architecture, troubleshooting.

I suspect there are more things you could add - let me know and I'll try to keep this list up to date!

No comments: