[GH-ISSUE #73] Support @ to identify server in argument #53

New issue

Open

opened 2026-03-14 01:10:41 +03:00 by kerem · 2 comments

kerem commented

2026-03-14 01:10:41 +03:00

Owner

Originally created by @sharego on GitHub (Jun 27, 2024).
Original GitHub issue: https://github.com/ameshkov/dnslookup/issues/73

Current, dnslookup uses fixed position for different arguments, first is domain, second is server, it likes nslookup command. However, sometime we forget this constraint.

The dig command use @ to set server, no position required, the we can use like this dnslookup @server domain [<providerName> <serverPk>] or dnslookup domain @server [<providerName> <serverPk>], or dnslookup domain server [<providerName> <serverPk>]

Originally created by @sharego on GitHub (Jun 27, 2024). Original GitHub issue: https://github.com/ameshkov/dnslookup/issues/73 Current, `dnslookup` uses fixed position for different arguments, first is domain, second is server, it likes `nslookup` command. However, sometime we forget this constraint. The `dig` command use `@` to set server, no position required, the we can use like this `dnslookup @server domain [<providerName> <serverPk>]` or `dnslookup domain @server [<providerName> <serverPk>]`, or `dnslookup domain server [<providerName> <serverPk>]`

kerem commented

2026-03-14 01:10:47 +03:00

Author

Owner

@ameshkov commented on GitHub (Jun 27, 2024):

I would generally prefer dig-like syntax, but it's a much bigger rework than just adding support for @.

@ameshkov commented on GitHub (Jun 27, 2024): I would generally prefer dig-like syntax, but it's a much bigger rework than just adding support for `@`.

kerem commented

2026-03-14 01:10:52 +03:00

Author

Owner

@sharego commented on GitHub (Jul 1, 2024):

Ok, Thanks

@sharego commented on GitHub (Jul 1, 2024): Ok, Thanks