O> Yes, the trick is specifying a DNS address as the last
O> parameter of nslookup (if using it in "batch" mode) or
O> using the "server" command in interactive mode
JdeBP> We are in the newsgroup for Microsoft DNS server, of course,
JdeBP> against which this trick will always work. But note that
JdeBP> this trick is not universally applicable.
O> Huh ... are you sure ?
Yes.
O>
http://www.stopspam.org/usenet/mmf/man/nslookup.html
What relevance did you think that that page has ?
O> and in any case we were talking about windows...
Read the first two sentences of what I wrote again.
JdeBP> It will not produce the desired results if one has "split
JdeBP> horizon" DNS service using either separate databases or
JdeBP> tagged database records.
O> Or bind views,
BIND's "views" mechanism _is_ "split horizon" DNS service using
separate databases. Read the web page that I pointed to again.
<URL:
http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-split-horizon.html#MultipleDatabases>
O> but .. if you issue the suggested nslookup command the DNS server
O> you're querying will see your NATted IP address
No-one has mentioned NAT except you, just now. There is no reason to
suppose that NAT is involved in any way, and even were NAT involved
there is no reason to suppose that the system hasn't been configured
to present the "internal" view of the DNS namespace to the publically
reachable IP address as well. As I said, the trick is not
universally applicable.
O> one may also use external tools to perform all the required
O> DNS checks [...]
As I said in my post:
JdeBP> The simplest way to determine what DNS data the rest
JdeBP> of Internet will actually see, even in such
JdeBP> configurations, is to employ the services of one of
JdeBP> the several promiscuous proxy DNS services that
JdeBP> various organizations supply to the whole of Internet.
<URL:
http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-obtaining-proxy-service.html>
thank you for that, just what the doctor ordered