Different results for q com NS vs q com. NS

[alex-feel]

I've noticed inconsistent behaviour when performing NS record queries using the q utility. The queries q com NS and q com. NS return different results.

Here are the results I get:

For q com NS:

. 142h41m30s NS a.root-servers.net.
. 142h41m30s NS b.root-servers.net.
. 142h41m30s NS c.root-servers.net.
. 142h41m30s NS d.root-servers.net.
. 142h41m30s NS e.root-servers.net.
. 142h41m30s NS f.root-servers.net.
. 142h41m30s NS g.root-servers.net.
. 142h41m30s NS h.root-servers.net.
. 142h41m30s NS i.root-servers.net.
. 142h41m30s NS j.root-servers.net.
. 142h41m30s NS k.root-servers.net.
. 142h41m30s NS l.root-servers.net.
. 142h41m30s NS m.root-servers.net.

And for q com. NS:

com. 47h7m22s NS a.gtld-servers.net.
com. 47h7m22s NS b.gtld-servers.net.
com. 47h7m22s NS c.gtld-servers.net.
com. 47h7m22s NS d.gtld-servers.net.
com. 47h7m22s NS e.gtld-servers.net.
com. 47h7m22s NS f.gtld-servers.net.
com. 47h7m22s NS g.gtld-servers.net.
com. 47h7m22s NS h.gtld-servers.net.
com. 47h7m22s NS i.gtld-servers.net.
com. 47h7m22s NS j.gtld-servers.net.
com. 47h7m22s NS k.gtld-servers.net.
com. 47h7m22s NS l.gtld-servers.net.
com. 47h7m22s NS m.gtld-servers.net.

This differs from the behaviour of the dig utility, which treats both queries as FQDNs and returns the same results.

My questions are:

1. Is this difference in behaviour intended?
2. Shouldn't q treat the domain name as an FQDN by default, even if it does not end with a period?

[natesales]

Indeed a bug! Will be fixed in an upcoming release tonight.