ENUM Test Setup

ENUM (RFC 6116) is a protocol developed by the IETF that uses the Internet DNS system to translate E.164 (i.e. ordinary) telephone numbers into IP addressing schemes (like SIP, H323 or Email).

Lets build an ENUM server quikly for testing ...

BIND installation on windows
BIND Configuration
ENUM-Lookup
ENUM Resolver
Dig command

DNS Test Setup for NAPTR, SRV, A Records

BIND installation on windows

Download latest BIND version from https://www.isc.org/downloads/

Unzip downloaded file or extract to a folder
Locate setup file BINDInstall.exe, right click on it and run it by choosing “Run as administrator”



Change the Target Directory.

Use complex passwords including capital, alphanumeric, special characters. Window policies sometimes restricts weak password and block installation. For example I used P@ssw0rd



Click on Yes when prompted.

You will get error if setup program cannot create Account for the Service.




The reasons of this error might be following

i)     you chose a week password that is not as per the password policies defined in windows. Choose a harder password which include alphanumeric and special character’s.

ii)     The setup program could not create required folders in path Target Directory provided by you. You may try with choosing another drive or path. Or make required directories manually (c:/dns/bin and c:/dns/etc). Note: Replace c:/dns with your desired path.

Setup program will take from few seconds to few minutes depending on your system setup and finally it will prompt “BIND installation completed successfully”



Click OK
Verify the Progress section in BIND Installer.



Click “Exit” on the BIND Installer window to exit from setup program.

BIND Configuration

From the DOS prompt, change directory to target path where you installed bind, use the command this way: (My install folder was c:\dns, you should change path in command as set by you

cd c:\dns\bin
rndc-confgen -a

which will create a rndc.key file in c:\dns\etc directory.



Now put following 02 files in c:\dns\etc directory.
Change directory to wherever you installed bind.
Change IP address to your IP where bind will listen.

named.conf
// NAME SERVER for WINDOWS options { directory "C:\dns\etc"; // version added for security, otherwise may be able to exploit known weaknesses version "not currently available"; pid-file "named.pid"; recursion yes; // alternatively use allow-recursion {192.188.2/24;}; (change IP as required) // or allow-recursion {"localnets"}; if your netmask is appropriate //listen-on {127.0.0.1;}; listen-on { 192.168.150.20;}; }; // log to named.log events from info UP in severity (no debug) // defaults to use 3 files in rotation // failure messages up to this point are in the event log logging{ channel my_log{ file "named.log" versions 3 size 250k; severity debug; print-time yes; print-severity yes; print-category yes; }; category default{ my_log; }; }; zone "e164.arpa" { type master; file "C:\dns\etc\db.e164.arpa"; };
db.e164.arpa
$TTL 86400 e164.arpa. IN SOA ns.e164.arpa. root.e164.arpa. ( 2004011522 ; Serial no., based on date 21600 ; Refresh after 6 hours 3600 ; Retry after 1 hour 604800 ; Expire after 7 days 3600 ; Minimum TTL of 1 hour ) e164.arpa. 43200 IN NS ns.e164.arpa. ; ns.e164.arpa. 43200 IN A 192.168.150.20 3.2.1.0.5.5.5.5.1.2.1.e164.arpa. IN NAPTR 10 100 "u" "E2U+pstn:sip""!^.*$!sip:+1-215-555-0123;npdi;rn=+5-155-555-0199@gwIP.com;user=phone!". 3.2.1.0.5.5.5.5.1.2.1.e164.arpa. IN NAPTR 15 100 "u" "E2U+pstn:sip""!^.*$!sip:+1-215-555-0123;npdi;rn=+5-255-555-0199@gwIP.com;user=phone!". 3.2.1.0.5.5.5.5.1.2.1.e164.arpa. IN NAPTR 3 100 "u" "E2U+pstn:sip""!^.*$!sip:+1-215-555-0123;npdi;rn=+5-355-555-0199@gwIP.com;user=phone!". 3.2.1.0.5.5.5.5.1.2.1.e164.arpa. IN NAPTR 5 100 "u" "E2U+pstn:sip""!^.*$!sip:+1-215-555-0123;npdi;rn=+5-455-555-0199@gwIP.com;user=phone!". 0.9.8.7.6.5.4.3.2.1.e164.arpa. NAPTR 10 100 "u" "E2U+sip" "!^.*$!sip:info@192.168.150.50!". 0.9.8.7.6.5.4.3.2.1.e164.arpa. NAPTR 10 101 "u" "E2U+h323" "!^.*$!h323:info@192.168.150.50!". 0.9.8.7.6.5.4.3.2.1.e164.arpa. NAPTR 10 102 "u" "E2U+msg" "!^.*$!mailto:info@192.168.150.50!". 8.1.2.7.5.9.3.3.1.6.1.e164.arpa. NAPTR 100 10 "U" "SIP+E2U" "!^.*$!sip:16133957218@192.168.150.50!". \\*.e164.arpa. NAPTR 10 100 "U" "E2U+sip" "!\\+(.+)!sip:\\1@192.168.150.50!". \\*.e164.arpa. NAPTR 10 100 "U" "E2U+sip" "!\\+(.+)!tel:+\\1!". *.e164.arpa. NAPTR 10 100 "U" "E2U+pstn:sip" "!\\+(.+)!sip:+\\1;npdi!". *.1.e164.arpa. NAPTR 10 100 "U" "E2U+pstn:sip" "!\\+(.+)!sip:+\\1;npdi!". *.*.*.e164.arpa. NAPTR 10 100 "U" "E2U+pstn:sip" "!\\+(.+)!sip:+\\1;npdi!".
Now you are ready to run service. Open services and start "ISC BIND" sevice.

ENUM Test Lookup

To test enum server installation use any of the following utilities.

ENUM Resolver

ENUM Resolver is an Electronic NUmber Mapping (ENUM) Lookup utility. You can download it from KaplanSoft.

 

Dig command

Use dig command for enum lookup, see example below ..

C:\dns\bin>dig @192.168.1.6 -t naptr 0.9.8.7.6.5.4.3.2.1.e164.arpa ; <<>> DiG 9.12.3-P1 <<>> @192.168.1.6 -t naptr 0.9.8.7.6.5.4.3.2.1.e164.arpa ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55853 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: de07aeaa053521fea211ef6b5c5725040753beb62a6e79f3 (good) ;; QUESTION SECTION: ;0.9.8.7.6.5.4.3.2.1.e164.arpa. IN NAPTR ;; ANSWER SECTION: 0.9.8.7.6.5.4.3.2.1.e164.arpa. 86400 IN NAPTR 10 102 "u" "E2U+msg" "!^.*$!mailto:info@192.168.150.50!" . 0.9.8.7.6.5.4.3.2.1.e164.arpa. 86400 IN NAPTR 10 101 "u" "E2U+h323" "!^.*$!h323:info@192.168.150.50!" . 0.9.8.7.6.5.4.3.2.1.e164.arpa. 86400 IN NAPTR 10 100 "u" "E2U+sip" "!^.*$!sip:info@192.168.150.50!" . ;; Query time: 2 msec ;; SERVER: 192.168.1.6#53(192.168.1.6) ;; WHEN: Sun Feb 03 22:59:40 India Standard Time 2019 ;; MSG SIZE rcvd: 265

 

Start testing now, test setup is ready. Don't forget to resart ISC Bind service whenever you edit the conf or db files.

END