Using "spec.dnsp.co"

spec.dnsp.co will always return a specific IP address. (For instance, to return the IP address 55.66.77.88 you would lookup "55.66.77.88.spec.dnsp.co") If you suspect a specific IP address is being noted and changed in your DNS traffic this will allow you to check. Both A and AAAA are supported. (for AAAA, use for instance 1111.2222.3333.4444.5555.6666.7777.8888.spec.dnsp.co). Anything that the parser can't parse will return 0.0.0.0 or ::0.


Syntax:

dig 10.20.30.40.spec.dnsp.co
nslookup 10.20.30.40.spec.dnsp.co
host 10.20.30.40.spec.dnsp.co

Examples:

prompt> dig 98.76.54.32.spec.dnsp.co ; <<>> DiG 9.5.0-P2 <<>> 98.76.54.32.spec.dnsp.co ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 150 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;98.76.54.32.spec.dnsp.co. IN A ;; ANSWER SECTION: 98.76.54.32.spec.dnsp.co. 0 IN A 98.76.54.32 ;; Query time: 65 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Mon Dec 22 02:41:03 2014 ;; MSG SIZE rcvd: 58
prompt> dig AAAA 9898.8787.7676.6565.5454.4343.3232.2121.spec.dnsp.co ; <<>> DiG 9.5.0-P2 <<>> AAAA 9898.8787.7676.6565.5454.4343.3232.2121.spec.dnsp.co ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 657 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;9898.8787.7676.6565.5454.4343.3232.2121.spec.dnsp.co. IN AAAA ;; ANSWER SECTION: 9898.8787.7676.6565.5454.4343.3232.2121.spec.dnsp.co. 0 IN AAAA 9898:8787:7676:6565:5454:4343:3232:2121 ;; Query time: 55 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Mon Dec 22 02:41:43 2014 ;; MSG SIZE rcvd: 98