JJ said:
On Windows XP, is there a log that describe the detailed log of the
network initialization phase of a dialup connection? The information
I need is the primary and secondary DNS addresses.
The reason I need it is because I already set my DNS to Google DNS
statically. I don't want to change it nor disconnect current
connection. I just want to know the "offered" DNS addresses at the
time the dialup is connected.
Right-click on the dial-up connectoid in the Network applet in Control
Panel. Select the Properties context menu item. Under the Networking
tab, select "Internet Protocol (TCP/IP)" and click Properties.
At that point, did you select to automatically get assigned an IP
address (a dynamically assigned IP address by the upstream DHCP server)
or did you enter an IP address so you have a static one? For the DNS
server specification, did you elect to have one dynamically assigned to
your host or did you select "Use the following DNS server addresses" and
specify some?
For the DNS setup, click on the Advanced button. Go to the DNS tab.
How many DNS servers do you have defined there? Here is where you
specify what DNS server(s) to use. Each connectoid can specify
differently whether it gets a dynamic or static assigned IP address,
uses a dynamically assigned DNS server or those you specify, in what
order the DNS servers are used, and other setup on a per-connectoid
basis.
If you specified the Google DNS server here and if you want that one
used first then make sure it is at the top of the list. Although you
might want to always use Google, sometimes a DNS lookup will fail so you
might want to specify a secondary DNS server (and even a third and
fourth). If you only want Google as your primary DNS server, I'd
suggest entering the IP address of your router (probably 192.168.1.1) as
a secondary DNS server. Your router is probably configured for dynamic
IP address assignment and DNS server assignment by your ISP's DHCP
server, so specifying your router as your secondary DNS server means it
fails the DNS lookup request (it always does this) to pass the request
further upstream which is to your ISP's DNS server. That way, if there
is a problem with the Google DNS server or it is unreachable (i.e., the
route to it doesn't work) then you have your ISP's DNS server (through
your router) as a backup.
My setup is probably similar to your own regarding DNS servers. My LAN
connectoid uses Google DNS as the primary and my router as the secondary
(and my router gets dynamically assign IP address and DNS server so it
forwards DNS requests to my ISP's DNS server). I used to have multiple
public DNS servers listed (Google, OpenDNS, DynDNS, Comodo, and another
one that I don't remember right now) but many like to redirect you their
"helper" web site if the DNS lookup fails. That lets them advertize on
failed DNS lookups (either with ads or tracking the clicks to record to
where you navigate for info sold to their customers). Even my ISP
defaults to redirecting to their "helper" page on a failed lookup but
their customers can opt out of that so-called feature (which I did).
That redirection violates DNS protocol which should be reporting a
failure to the client, not a success by redirection to elsewhere. So
I've trimmed down to just Google (which doesn't redirect on a failed
lookup) and my router (which goes to my ISP's DNS server).
I haven't used a dial-up connection in maybe 15-20 years. Others have
suggested you use "ipconfig.exe /all" to get info on your IP address,
DNS server, and other network info. Since that only shows info for
network adapters that are currently active, you won't see any info for
the dial-up connection until after you establish that connection.
Nirsoft's AdapterWatch also gives you networking info but, again, I
don't think you'll see your dial-up connectoid listed until it is active
(i.e., after you have a binding to it).
I suspect an easy way to see which DNS server you are using is to ask it
to resolve an IP address or hostname. In a command shell, do a DNS
lookup using the 'nslookup' command, as in:
nslookup
www.yahoo.com
nslookup 209.191.122.70
The 2nd instance is only to test if your DNS server will do a reverse
DNS lookup (IP address to hostname). Sometimes you get a hostname where
you want to check what is its IP address but you also want to check if
its IP address resolves back to the same hostname or to something else.
The first line of output from nslookup tells you which DNS server to
which you sent the lookup request. For the normal use (where you get
the IP address for a specified hostname), you'll get output that looks
like the following:
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
Name: ds-any-fp3-real.wa1.b.yahoo.com
Addresses: 209.191.122.70, 98.139.183.24
Aliases:
www.yahoo.com, fd-fp3.wg1.b.yahoo.com, ds-fp3.wg1.b.yahoo.com
ds-any-fp3-lfb.wa1.b.yahoo.com
The "Server:" line tells you which DNS server you used. You can specify
the DNS server to use for the lookup by running nslookup without any
command-line parameters to go into its interactive mode ("nslookup" with
nothing after it goes into its interactive mode). Because you specified
on the command line what to lookup, it uses the default DNS server.