On 06/06/2017 15:07, Jason Welsh wrote:
ugh, the upgrade changed the owner from named to root on /var/named
where my zone files are and
therefore named could not read the zone files.. How embarrassing.. ;)
Jason
That will happen every time named is restarted (it is part of the start
up
ugh, the upgrade changed the owner from named to root on /var/named
where my zone files are and
therefore named could not read the zone files.. How embarrassing.. ;)
Jason
On 06/06/2017 09:58 AM, Kenneth Porter wrote:
--On Tuesday, June 06, 2017 10:53 AM -0400 Jason Welsh
wrote:
[root
--On Tuesday, June 06, 2017 10:53 AM -0400 Jason Welsh
wrote:
[root@bind1 /var/named]$nslookup -port=5353 servername 10.115.76.87
nslookup is deprecated. What does dig say? It's much more informative and
shows all the details of the query and reply packets.
---
This email has been check
hey folks, we upgraded bind last night to bind-9.8.2-0.62.rc1.el6_9.1.x86_64
and now our server seems to not be able to update. Whenever we add
records and update the soa and reload,
it still shows the old data..
so for example, we have
[root@bind1 /var/named]$grep servername domainname.net.zon
4 matches
Mail list logo