I’m not that lucky.
have you tried running nslookup in interactive mode?
I haven’t prior to this evening, but it seems to produce results:
> www.comodo.com.
Server: [8.26.56.26]
Address: 8.26.56.26
------------
SendRequest(), len 32
HEADER:
opcode = QUERY, id = 3, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
www.comodo.com, type = A, class = IN
------------
------------
Got answer (143 bytes):
HEADER:
opcode = QUERY, id = 3, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 1, authority records = 4, additional = 0
QUESTIONS:
www.comodo.com, type = A, class = IN
ANSWERS:
-> www.comodo.com
type = A, class = IN, dlen = 4
internet address = 91.199.212.176
ttl = 536 (8 mins 56 secs)
AUTHORITY RECORDS:
-> comodo.com
type = NS, class = IN, dlen = 19
nameserver = ns0.comododns.net
ttl = 751 (12 mins 31 secs)
-> comodo.com
type = NS, class = IN, dlen = 16
nameserver = ns1.comododns.com
ttl = 751 (12 mins 31 secs)
-> comodo.com
type = NS, class = IN, dlen = 6
nameserver = ns0.comododns.com
ttl = 751 (12 mins 31 secs)
-> comodo.com
type = NS, class = IN, dlen = 6
nameserver = ns1.comododns.net
ttl = 751 (12 mins 31 secs)
------------
Non-authoritative answer:
Name: www.comodo.com
Address: 91.199.212.176
However, I don’t get entirely repeatable results when I try to lookup 8.26.56.26:
On the first try:
> 8.26.56.26
Server: [8.26.56.26]
Address: 8.26.56.26
------------
SendRequest(), len 41
HEADER:
opcode = QUERY, id = 9, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
26.56.26.8.in-addr.arpa, type = PTR, class = IN
------------
------------
Got answer (41 bytes):
HEADER:
opcode = QUERY, id = 9, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
26.56.26.8.in-addr.arpa, type = PTR, class = IN
------------
*** No address (A) records available for 8.26.56.26
On the next try:
> 8.26.56.26
Server: [8.26.56.26]
Address: 8.26.56.26
------------
SendRequest(), len 41
HEADER:
opcode = QUERY, id = 10, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
26.56.26.8.in-addr.arpa, type = PTR, class = IN
------------
------------
Got answer (41 bytes):
HEADER:
opcode = QUERY, id = 10, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
26.56.26.8.in-addr.arpa, type = PTR, class = IN
------------
*** [8.26.56.26] can't find 8.26.56.26: Non-existent domain
It’s all interesting output, and it’s clear that the server certainly does
work. However, I’m not sure how all of this speaks to the issue I’m
experiencing. In this case, it would be nice to have a background app
that monitors DNS usage, so I could see if Windows is really kicking it
out entirely, or just during nslookups. If it just doesn’t want to use
8.26.56.26 as a primary, then I might just as well swap it out with
something that does work.
Or, better yet, someone could just give the darned thing a name. :-\
Regards.
