Using "increment.dnsp.co"

"increment.dnsp.co" will increase by one each time it is queries. Notice that this may increment by more than one from your perspective (increments of 2 are common as some DNS servers query twice, or maybe somebody else is running a test as well). Regardless, it should never go down or stay the same until it reaches the maximum size and ticks back over to 0.0.0.0. Both A and AAAA requests are supported.


Examples:

prompt> dig increment.dnsp.co ; <<>> DiG 9.8.3-P1 <<>> increment.dnsp.co ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60280 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;increment.dnsp.co. IN A ;; ANSWER SECTION: increment.dnsp.co. 0 IN A 0.0.0.3 ;; Query time: 60 msec ;; SERVER: 192.168.2.1#53(192.168.2.1) ;; WHEN: Sun Dec 21 19:38:17 2014 ;; MSG SIZE rcvd: 51 prompt> dig increment.dnsp.co ; <<>> DiG 9.8.3-P1 <<>> increment.dnsp.co ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40932 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;increment.dnsp.co. IN A ;; ANSWER SECTION: increment.dnsp.co. 0 IN A 0.0.0.4 ;; Query time: 44 msec ;; SERVER: 192.168.2.1#53(192.168.2.1) ;; WHEN: Sun Dec 21 19:38:17 2014 ;; MSG SIZE rcvd: 51