ddns-rev-domainname being created wrong.

Applications IP Networking
1

Greetings all,

I have been battling with this problem for some time now, and I am not sure if I am just not seeing the obvious anymore or have made a stupid mistake, but I just can seem to get the reverse address in my network to run the right way.

Short description of my network:
I have a 50 user network with two switches and a main server connected to the internet with DSL. 99% of the user are on windows.

I have setup the main server as the main DNS with bind and Dynamic DHCP. A couple of the network maschines are internal servers, one for development, one as a NAS etc.

Manual DNS entries has been made for the internal servers and a couple of printers and routers, all other clients are assigned a IP via DHCP.

The problem:
All the clients are recieving the right IP on the subnet 192.168.1.0 but the reverse adresses are wrong, ie: 164.1.168.192.1.168.192.in-addr.arpa :frowning:

Now I know that this is the cause of a single dot that is not there, but I don't know where to look anymore. I am just not sure anymore what I can do.

The network runs, but windows take a long time to get a lease from the server (due to the reverse lookup not working)

dhcpd.conf

authoritative;
ddns-update-style interim;
ddns-updates on;
ddns-domainname "mynet";
ddns-rev-domainname "1.168.192.in-addr.arpa";
ddns-hostname = pick (option fqdn.hostname, option host-name, concat ("dhcp-",binary-to-ascii (10, 8, "-", leased-address)));
update-static-leases on;
option domain-name "mynet";
option domain-name-servers 192.168.1.1;
option ntp-servers 192.168.1.1;
option netbios-node-type 8;
option host-name = config-option server.ddns-hostname;
include "/etc/rndc.key";
#DSL subnet ip replaced with x
subnet xxx.xxx.xxx.xxx netmask 255.255.255.0 {
}
subnet 192.168.1.0 netmask 255.255.255.0 {
        ddns-domainname "mynet";
        ddns-rev-domainname "1.168.192.in-addr.arpa";
        range 192.168.1.32 192.168.1.192;
        default-lease-time 1800;
        max-lease-time 3600;
        option routers 192.168.1.1;
        option ip-forwarding off;
        option broadcast-address 192.168.1.255;
        option subnet-mask 255.255.255.0;
        option ntp-servers 192.168.1.1;
        zone mynet {
                primary 192.168.1.1;
                key rndc-key;
        }
        zone 1.168.192.in-addr.arpa {
                primary 192.168.1.1;
                key rndc-key;
        }
        option netbios-name-servers 192.168.1.1;
}
host mainserver {
        hardware ethernet 00:1A:A0:27:F9:D7;
        fixed-address 192.168.1.1;
        option domain-name "mynet";
}
host devserver {
        hardware ethernet 00:22:15:78:ff:9a;
        fixed-address 192.168.1.3;
        option domain-name "mynet";
}
2

Maybe he knows how to reverse an IP, does not need your help?

 
ddns-rev-domainname "in-addr.arpa";

Are you adnet or mynet?

1 Like
3

:o, sorry changed the values.. the network is mynet.

Thanks for the tip, I tried it and it seems to have worked... Great !!! :smiley: I changed it int the genral section and the subnet, and it seems to work perfect. Thanks a million :b:

4

Such declarations seem silly, as they never change, but it is good style to declare constants in one section with mnemonic names, and not hard code them elsewhere.

The only thing that gets tricky in DNS is when 2 nets are on one reverse domain, when subnetting not modulo 256. Similarly, sometimes a.b.c.d is defined on the c.d domain server, as there is no b.c.d name server.

I always did it by hand!