Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Reverse DNS resolution issue

Status
Not open for further replies.

yumbelie

Programmer
Dec 31, 2002
96
GB
Hi. I've got my DNS server almost working, problem is it currently isn't working on reverse DNS requests. Forward are fine, e.g.:

> ns1.mynameserver.com
Server: ns1.mynameserver.com
Address: 0.0.0.0

Name: ns1.mynameserver.com
Address: 17.18.19.1

>

But reverses fail, if I put in 17.18.19.1 I get:

> 17.18.19.1
Server: ns1.mynameserver.com
Address: 0.0.0.0

*** ns1.mynameserver.com can't find 17.18.19.1: Non-existent host/domain
>

Now, I've configured named.conf (it's freeBSD I'm using), the two bits of interest are configured as follows:

// Forward DNS for domain

zone "mynameserver.com" {
type master;
file "mynameserver.com";
};

// Reverse DNS for domain

zone "19.18.17.in-addr.arpa" {
type master;
file "reverse-mynameserver.com";
};

The two files: mynameserver.com & reverse-mynameserver.com are configured as follows:

mynameserver.com ->
-----------------------

; Domain Name Setup
$TTL 604800
mynameserver.com. IN SOA ns1.mynameserver.com. root.mynameserver.com. (
2003061201 ; Serial
10800 ; Refresh 10800 secs
7200 ; Retry
86400 ) ; Expire (100 Days)
; DNS Servers
IN NS ns1.mynameserver.com.
; Machine Names
localhost IN A 127.0.0.1
ns1 IN A 17.18.19.1
@ IN A 17.18.19.1
testmachine IN A 17.18.19.118

; Aliases
moonshine IN CNAME @

reverse-mynameserver.com
---------------------------

; Domain Name Setup
$TTL 604800
@ IN SOA ns1.mynameserver.com. root.mynameserver.com. (
2003061201 ; Serial
10800 ; Refresh 10800 secs
7200 ; Retry
86400 ) ; Expire (1 Days)
; Reverse Lookup
IN NS ns1.mynameserver.com.
1 IN PTR ns1.mynameserver.com.

I cannot see what the problem is, I'm sure it should be correct - but perhaps one of you experts could shed some light? Incidentally, I am doing the nslookups on my nameserver locally, so I know the fault lies locally, not elsewhere.
 
Resolved it, I had incorrectly specified the reversed zone IP of the reverse lookup file in named.conf. Always worth checking that.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top