peterknowles.ca

Hey Folks,

To setup a PTR record (reverse lookup) you need to create a special zone for it.

For the following information, we’re going to use the following IP address and hostname for reference purposes.

IP Address: 12.34.56.78
Hostname: mydomain.com

Okay — with the information, you’d create a new zone with the name:

78.56.34.12.in-addr.arpa. (the final “.” is very important)

This should create a default zone which looks like:

78.56.34.12.in-addr.arpa. A 1 86400 12.34.56.78
www.78.56.34.12.in-addr.arpa. A 1 86400 12.34.56.78
78.56.34.12.in-addr.arpa. NS 1 86400 ns1.us.editdns.net.
78.56.34.12.in-addr.arpa. NS 1 86400 ns2.us.editdns.net.
78.56.34.12.in-addr.arpa. NS 1 86400 ns3.us.editdns.net.

Next, you want to remove both “A” records which are not needed for the reverse lookup zone.

Finally add a “PTR” record with:

78.56.34.12.in-addr.arpa. PTR 1 86400 mydomain.com.

The resulting zone should look something like this:

So long as your ISP hasn’t imposed some odd restriction, and ns1.us.editdns.net is listed as your SOA for this domain, then everything should resolve without an issue within 2 – 3 days.

Now, you can add the “forward” zone with the name:

mydomain.com. (the final “.” is very important)

Also to save you a step, add the “default ip” as “12.34.56.78″.

This should create a default zone which looks like:

You can test to see if each of the editdns.net servers is properly configured along the way by running the following commands from the windows command line:

nslookup 12.34.56.78 ns1.us.editdns.net
nslookup 12.34.56.78 ns2.us.editdns.net
nslookup 12.34.56.78 ns3.us.editdns.net

(the above focuses on the “US” servers. if using the “EU” servers, simply follow same instructions making sure that the relevent “EU” records are listed and setup the same as the “US” within the zone.)

Hope this helps!

admin EditDNS.net API

Hey Folks,

I just thought I’d post a sample I developed over the past day hopefully to spark some feedback and more importantly to show you one of the cool new features of the upcoming EditDNS.net 2.0 API.

One of the neat features I’ve developed into the new API is the ability to switch between, PHP serialized, PHP raw (arrays output to screen) and XML.

XML will be the default as it allows the most usability across various programming languages.

So here we go, a simple request for my zone records.

(These records are not actually a complete list of live records but are merely a sample put together during the development stages.)

PHP Serialized:
http://editdns.tpnh.com/api/2/8414/index.php?cmd=getzonerecords&apikey=123&zoneid=1&format=php

PHP Raw:
http://editdns.tpnh.com/api/2/8414/index.php?cmd=getzonerecords&apikey=123&zoneid=1&format=php_raw

XML:
http://editdns.tpnh.com/api/2/8414/index.php?cmd=getzonerecords&apikey=123&zoneid=1&format=xml

or

http://editdns.tpnh.com/api/2/8414/index.php?cmd=getzonerecords&apikey=123&zoneid=1

Okay, so let’s go over the above.

First off, I’m developing this on my own server so don’t go jotting down my web address for production purposes, as it’ll kind of be useless since I don’t actually poll against the live database in these development snapshots.

That aside, here’s the basic file structure I’ve used for the development server:

2 => version number
8414 => build number (this is YYMMDD format)

Now here’s the arguments used by the script.

cmd => this is the command we want to execute. in my sample this is “getzonerecords”.

apikey => this is your unique api key created through the editdns.net admin. remember this is a development server so your api key will not work for my sample.

zoneid => this is the numeric zone id for your domain zone. for our sample, we’re using “1″.

format => this is the format you want the response to be sent back in. this can be “php”,”php_raw” or “xml”. if not specified, it’ll default to “xml”.

Easy as pie!

Until next time…

–
Best Regards,
Peter

admin EditDNS.net API

Hi,

I’m working on the next version of the EditDNS.net API which is going to be far more advanced than the current dated one.

The API is going to have 4 types of commands:

GET – these will be used whenever we need to acquire some existing data such as zones, or zone records.

ADD – these will be used whenever we need to add a new record such as a zone, or zone record.

EDIT – these will be used whenever we need to update an existing record such as a zone, or zone record.

DELETE – these will be used whenever we need to delete a record such as a zone, or zone record.

Pretty self explanatory right?

Please feel free to follow this blog or my post at:

http://forums.nerdie.net/showthread.php?t=973

Let me know of your specific needs, and I’ll work to ensure these features are prioritized during the development.

Also anyone intertested in offering financial assistance, please contact me at: pknowles@peterknowles.ca

–
Best Regards,
Peter Knowles

admin EditDNS.net API