Tuesday 26 February 2013

finding the time to live TTL on a DNS record in windows

If you need to find the time to live on a DNS record in windows you can click
start -> administrative tools -> DNS
Click View -> Advanced
Now right click on your record and click properties
The TTL will be displayed

Alternatively
nslookup -q=a -debug www.mydomain.com

nslookup -q=mx -debug email.mydomain.com

nslookup -q=ns -debug ns.mydomain.com

In linux you can use the dig command


Monday 25 February 2013

investigating public IP addresses with ripe.net

If you come across a public IP address but your not sure what it is you can use tools such as ripe.net to investigate. In this example, I'm going to attempt to look up yahoo.com (98.138.253.109).

Go to http://www.ripe.net/
In the RIPE database section enter the IP address you want to investigate and click search.
If the details are held by RIPE they will be displayed
Sometimes the IP details are held by another provider
In that case the provider will be listed
In my case it was http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml
I went to iana.org. My IP starts with 98 the page tells me this is held by http://whois.arin.net
I went to http://whois.arin.net/ui entered the IP address into the search bar and click search
This brought up the details of who owns that IP address which of course was Yahoo inc.

There are plenty of other web applications that help you get this information I've found that  http://network-tools.com to be useful.

Thursday 14 February 2013

Error 113 (net::ERR_SSL_VERSION_OR_CIPHER_MISMATCH): Unknown error in google chrome when connecting to Cisco ASDM


Looks like the default ssl encryption is set to des-sha1. 

Run the following to see what yours is set to:
#sh run | i ssl encryption. 

I was connecting my laptops ethernet port to the management port on the ASA.
My IP address settings were set to obtain. The ASA gave me an IP address. I connected to the ASA with the console cable to run the commands.


des has been broken for ages now. Looks like chrome won't connect unless you use a good encryption. I did the following to resolve:

#conf t
#ssl encryption aes128-sha1  (you can use higer if you want)
#wr mem

Now open chrome and go to https://192.168.1.1/admin