Skip to main content

Resolve list of hostnames to IP addresses

Recently I needed to check if a large number of hostnames were resolving to valid IP addresses on an internal network. This is what I came up with:


for /F %i in (names.txt) do @echo %i & nslookup %i | findstr /n "Address" | findstr /b "5"


The output looks as follows: 



TESTBOX1
5:Address:  10.11.20.43
TESTBOX2
5:Address:  10.11.20.44
TESTBOX3
5:Address:  10.11.20.45
TESTBOX4
*** dnsbox1.lab.local can't find TESTBOX4: Non-existent domain


As we can see first three records resolve. The fourth one doesn't have DNS record. 

For this to work, each hostname must be on a separate line in a text file "names.txt" and the command must be run from directory where the file sits. Alternatively you can specify full path (i.e c:\names.txt).

Let's break it down and see what's actually going on. 

We use for /f loop to parse names.txt and assign each line to variable %i, we then suppress output  (@echo) of nslookup and parse it to output only lines containing word Address (findstr /n), we also prepend a number of the line the matching string was found on. Then we again parse the output to display only lines starting with 5.  

This is what we get if we break the command down to separate chunks:

Here we only output file contents. 

for /F %i in (names.txt) do @echo %i

TESTBOX1
TESTBOX2
TESTBOX3
TESTBOX4


Here we display full nslookup output:


for /F %i in (names.txt) do @echo %i & nslookup %i



TESTBOX1
Server:      dnsbox1.lab.local
Address:  10.11.20.43
TESTBOX2
Server:      dnsbox1.lab.local
Address:  10.11.20.44
TESTBOX3
Server:      dnsbox1.lab.local
Address:  10.11.20.45
TESTBOX4
Server:      dnsbox1.lab.local
*** dnsbox1.lab.local can't find TESTBOX4: Non-existent domain


Here we display full nslookup output with numbered lines:

for /F %i in (names.txt) do @echo %i & nslookup %i | findstr /n "Address"

TESTBOX1
2:Address:  10.10.10.10
5:Address:  10.11.20.43
TESTBOX2
2:Address:  10.10.10.10
5:Address:  10.11.20.44
TESTBOX3
2:Address:  10.10.10.10
5:Address:  10.11.20.45
TESTBOX4
*** dnsbox1.lab.local can't find TESTBOX4: Non-existent domain
2:Address:  10.10.10.10


If we want to query specific DNS server (replace [DNSsrv] with correct IP/name)

for /F %i in (names.txt) do @echo %i & nslookup %i [DNSsrv] | findstr /n "Address" | findstr /b "5"


If you want to use it in a batch file you've to specify variables with double percentage sign ("%%i).


Comments

Popular posts from this blog

x.509 Certificates - Critical vs non-critical extensions

Extensions are used to associate additional information with the user or the key.  Each certificate extension has three attributes - extnID, critical, extnValue extnID - Extension ID - an OID that specifies the format and definitions of the extension critical - Critical flag - Boolean value extnValue - Extension value  Criticality flag specifies whether the information in an extension is important. If an application doesn't recognize the extension marked as critical, the certificate cannot be accepted. If an extension is not marked as critical (critical value False) it can be ignored by an application. In Windows, critical extensions are marked with a yellow exclamation mark,  View certificate extensions using OpenSSL: # openssl x509 -inform pem -in cert.pem -text -noout (output abbreviated)         X509v3 extensions:             X509v3 Key Usage: critical                 Digital Signature, Key Encipherment             X509v3 Subject Key Identifier

Cisco ASA Certificate Revocation Checking

ASA supports status verification using CRLs and OCSP. CRL can be retrieved using HTTP, LDAP or SCEP. Revocation checking using CRL: Over HTTP: ciscoasa(config)# crypto ca trustpoint ASDM_TrustPoint2 ciscoasa(config-ca-trustpoint)# revocation-check crl ciscoasa(config-ca-crl)# protocol http By default ASA will use address listed in CDP extension of the certificate that is being validated.  To override default behaviour we need to add the following in the CRL configuration context. ciscoasa(config-ca-crl)# policy static ciscoasa(config-ca-crl)# url 1 http://cdpurl.kp.local/crl.crl Over LDAP: Certificate I'm using for this lab, doesn't have LDAP address in its CDP extension. Therefore I'm using "policy static"  to specify LDAP URL where CRL can be retrieved.  ciscoasa(config)# crypto ca trustpoint ASDM_TrustPoint2 ciscoasa(config-ca-trustpoint)# revocation-check crl ciscoasa(config-ca-trustpoint)# crl configure ciscoasa

Count number of lines - 'findstr'

How do I count number of lines in a command output? findstr /r/n "^" | find /c ":" Above commands will display number of lines output by whatever command (well, nearly whatever) you specify in the front.  For example:  C:\>ping localhost | findstr /r/n "^" | find /c ":" FINDSTR: // ignored 12 This comes handy if you want to find out how many OUs you have in Active Directory: dsquery ou  -limit 0 | findstr /r/n "^" | find /c ":" How many user accounts there are: dsquery user -limit 0 | findstr /r/n "^" | find /c ":" Computers: dsquery computer -limit | findstr /r/n "^" | find /c ":"