Score:0

Why would DNS fail on the DNS server, but not on a host using the same DNS server?

in flag

I have set up Bind on a server running Centos Stream. The server has two interfaces, one to a corporate network and the other a private network. The DNS is set up for the private (192.168.0.0) network.

On the DNS server (192.168.0.2)

> nslookup test-serv9

;; Got SERVFAIL reply from 10.1.1.2, trying next server
Server:     192.168.0.2
Address:    192.168.0.2#53

** server can't find test-serv9: REFUSED 

On a client computer on the private network using the local DNS server (192.168.0.2), I can us nslookup to find a host:

> nslookup test-serv9

Server:     192.168.0.2
Address:    192.168.0.2#53

Name: test-serv9.test.company.example
Address: 192.168.0.100

The resolv.conf file from the DNS server

# Generated by NetworkManager
search company.example
nameserver 10.1.1.2
nameserver 192.168.0.2

The resolv.conf file from the client

# Generated by NetworkManager
search test.company.example
nameserver 192.168.0.2

Is the sub-domain the issue?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.