Author Topic: Test DNS setup is not giving reverse lookup  (Read 2886 times)


  • Zen Apprentice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Test DNS setup is not giving reverse lookup
« on: May 23, 2016, 10:24:49 am »

i have installed a test DNS setup with zentyal.
created domain and and added host name under that.

i have 2 domains and one is for windows and another one is for linux.

The machine added under windows DNS domains is resolving properly(forward and reverse)

But the domain created for Linux domain is not giving reverse lookup. how can i fix this.

when i am trying

Code: [Select]
[root@ZKWIPAMSTR01 ~]# nslookup

** server can't find NXDOMAIN

and here is the successful windows server resolution
Code: [Select]
[root@ZKWIPAMSTR01 ~]# nslookup
Address:    name =


  • Zen Apprentice
  • *
  • Posts: 22
  • Karma: +1/-0
    • View Profile
Re: Test DNS setup is not giving reverse lookup
« Reply #1 on: September 02, 2016, 12:37:58 am »
I possibly have the same problem. I noticed my Zentyal server has an extra octet in the IP adddress in DNS, at least when I look from Windows 7.  So far I haven't figured out how to fix it.

The named.conf.local shows:

acl "internal-local-nets" {;

dlz "AD DNS Zone" {
    database "dlopen /usr/lib/x86_64-linux-gnu/samba/bind9/";

zone "" {
    type master;
    file "/var/lib/bind/db.1.1.10";
    update-policy {
        // The only allowed dynamic updates are PTR records
        grant aero.tsi.awd. subdomain PTR TXT;
        // Grant from localhost
        grant local-ddns zonesub any;

The actual zone file shows:

scottz@zentyal:/var/lib/bind$ more db.1.1.10
$TTL 259200     ; 3 days     IN SOA (
                                2016053110 ; serial
                                28800      ; refresh (8 hours)
                                7200       ; retry (2 hours)
                                2419200    ; expire (4 weeks)
                                86400      ; minimum (1 day)
$TTL 3600       ; 1 hour
102                     PTR

The weird thing is, if I look from Server 2003, it's different.

I'm confused.  I'm sure I set something up wrong back in the day, that 2003 server has been around since 2003 came out, and it was migrated from 2000.  That said, I sure would like to fix the reverse lookup.

I have the zone also replicating to a Synology DNS server, and that does reverse lookup just fine.