;; Got SERVFAIL reply from 127.0.0.1, trying next server

[Kfir Lavi]

Hi,

boss doesn't resolve.
This cause the node to fail connecting the boss to identify itself.

boss ~ $ nslookup boss
;; Got SERVFAIL reply from 127.0.0.1, trying next server
Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find boss: NXDOMAIN

boss ~ $ nslookup boss.banshee.4g4g.com
;; Got SERVFAIL reply from 127.0.0.1, trying next server
;; Got SERVFAIL reply from 127.0.0.1, trying next server
Server: 10.0.0.23
Address: 10.0.0.23#53

** server can't find boss.banshee.4g4g.com: NXDOMAIN

Reverse lookup does work:

boss ~ $ nslookup 192.168.1.149
Server: 127.0.0.1
Address: 127.0.0.1#53

149.1.168.192.in-addr.arpa name = boss.banshee.4g4g.com.

I have edited banshee.4g4g.com.internal.db.head and ran named_setup
boss namedb $ cat banshee.4g4g.com.internal.db.head
boss IN A 192.168.1.149
ops IN A 192.168.1.150
cisco1 IN A 192.168.1.254

banshee.4g4g.com.internal.db did generate well.

Netstat shows named listenning on the localhost, internal and external
ip's.

boss namedb $ cat /etc/resolv.conf
domain banshee.4g4g.com
search banshee.4g4g.com
nameserver 127.0.0.1
nameserver 10.0.0.23
nameserver 194.90.1.5
nameserver 212.143.212.143

As it was explained we added a line to dhcpcd.conf to add 'nameserver
127.0.0.1'

Regards,
Kfir

[Robert Ricci]

Sounds like your boss is not running named (our install process sets up
the state to start it up), and/or 4g4g.com has not delegated the
subdomain boss.banshee.4g4g.com to your boss.

[Kfir Lavi]

Hi Robert and thanks for replaying.
ops and boss get their ip via dhcp from our office dhcp server.
For now I care mostly that node1 will be able to resolve boss ip.
Can you give me an example what I need to do.
I really tried to modify the db inside namedb directory, but nothing helps.

Kfir

[Kfir Lavi]

It is solved.
The NS line solved the problem:

IN NS boss.banshee.4g4g.com.

And this is how the file /etc/namedb/banshee.4g4g.com.internal.db.head
should look:

boss namedb $ cat /etc/namedb/banshee.4g4g.com.internal.db.head
$TTL 3600
@ IN SOA boss.banshee.4g4g.com. ops.banshee.4g4g.com. (
1 ; serial number
3600 ; refresh
3600 ; retry
1209600 ; expire
3600 ; negative
)
IN NS boss.banshee.4g4g.com.

boss IN A 192.168.1.149
ops IN A 192.168.1.150
cisco1 IN A 192.168.1.254

After changing head file, we need to run named_setup to regenerate
named files and restart service.

Kfir

> >> I have edited banshee.4g4g.com.internal.db.**head and ran named_setup
> >> boss namedb $ cat banshee.4g4g.com.internal.db.**head