similar to: Proper configuration for DNS slaves and masters

I have introduced some error in my dns resolution and I would like some help fixing it as I cannot seem to detect what I have done wrong. Briefly the setup is this: name servers: DNS01 - 216.185.71.33 DNS02 - 209.47.176.33 DNS03 - 216.185.71.34 DNS04 - 209.47.176.34 - offline DNS01 is a master DNS02-04 are slaves of 216.185.71.33 All are listed as authoritative for the zone test.com The

I am trying to sort out a configuration problem with y slave servers, more on that in a following message, but while I was examining the system log on one of those servers I saw this: Nov 3 12:30:43 inet04 named[18110]: client 174.88.12.107#60136: query (cache) 'www.soundunwound.com/A/IN' denied Nov 3 12:30:43 inet04 named[18110]: client 174.88.12.107#60140: query (cache)

This morning I discovered this in the logwatch report for our external MX backup host. STARTTLS: write error=syscall error (-1), errno=32, get_error=error:00000000:lib(0):func(0):reason(0), retry=99, ssl_err=5: 206 Time(s) I also see many entries similar to this: 8: fl=0x802, mode=140777: SOCK inet04.mississauga.harte-lyne.ca/34091->(Transport endpoint is not connected): 1 Time(s)

Kernel 2.6.18-308.8.2.el5 I recently experienced an odd problem with a host at our warm-site location. The facility we use suffered an hvac failure during elevated ambient temperatures (30C+) on Monday past and the equipment room reportedly cooked for some hours. It was sufficient that our equipment shutdown. In all probability this was due to an over-temp condition since the systems are all

Am 25.11.2014 um 21:39 schrieb James B. Byrne: > This morning I discovered this in the logwatch report for our external MX > backup host. > > > STARTTLS: write error=syscall error (-1), errno=32, > get_error=error:00000000:lib(0):func(0):reason(0), retry=99, ssl_err=5: 206 > Time(s) > > > > I also see many entries similar to this: > > > > 8:

CentOS-6.6 We have a host that has multiple IPv4 addresses aliased to eth0. The primary address is 216.185.71.x and the alias is 192.168.6.x. This host connects to devices on both netblocks without problems. Only default routing is used and it looks like this: #ip route 192.168.6.0/24 dev eth0 proto kernel scope link src 192.168.6.x 216.185.71.0/24 dev eth0 proto kernel scope link src

I am seeing this in the syslog when starting a multi-homed CentOS-5.3 host. Oct 6 08:35:04 inet04 nm-system-settings: initial_add_devices_of_type: could not get device from HAL: An SELinux policy prevents this sender from sending this message to this recipient (rejected message had interface "org.freedesktop.Hal.Manager" member "FindDeviceByCapability" error name

This morning I see this in the syslog on our primary public DNS host. internal_send: 142.77.1.1#33950: Connection timed out: 1 Time(s) internal_send: 142.77.1.1#35153: Connection timed out: 1 Time(s) internal_send: 142.77.1.1#35644: Connection timed out: 1 Time(s) internal_send: 142.77.1.1#49394: Connection timed out: 1 Time(s) internal_send: 142.77.1.1#49816: Connection timed

Hi James, Simply remove the GATEWAY line from the eth0:192 interface config :D Then you'll had only one default gateway. And the source IP to all unknown address will be the routeable one. Att., Antonio. ----- "James B. Byrne" <byrnejb at harte-lyne.ca> escreveu: > De: "James B. Byrne" <byrnejb at harte-lyne.ca> > Para: centos at

I am seeing these in smb.log and each time I do it appears that the user in question is unable to retrieve their roaming profile. Does anyone know what is going on and more importantly, how to cure it? . . . [2017/03/28 16:24:37.426162, 0] ../source3/smbd/oplock.c:713(oplock_timeout_handler) Oplock break failed for file Administrator/AppData/Roaming/Microsoft/Internet Explorer/Quick

We have a bunch of lists hosted on a CentOS-4.9 server running sendmail and mailman that we are moving to a CentOS-6 vm running postfix and mailman. I am testing the setup and I am running into a problem no doubt caused by my own ignorance wrt postfix. Based on groking the web I discovered that the recommended way to configure postfix to work with mailman is a script called

At ~07:40 (UTC-4:00) this morning our gateway host lost its WAN Ethernet adaptor. Subsequent to recovery, which required a reboot, the following entries were find in /var/log/messages: Jun 6 07:39:50 gway02 kernel: PING_FLOOD: IN=eth0 OUT= MAC=00:25:90:61:74:c0:00 :24:14:2b:f2:80:08:00 SRC=74.205.112.125 DST=216.185.71.33 LEN=64 TOS=0x00 PREC= 0x00 TTL=50 ID=30954 PROTO=ICMP TYPE=8 CODE=0

[root at smb4-1 ~ (master)]# samba-tool dns query localhost brockley.harte-lyne.ca brockley.harte-lyne.ca ALL -U administrator Password for [BROCKLEY\administrator]: Name=, Records=4, Children=0 SOA: serial=3, refresh=900, retry=600, expire=86400, minttl=3600, ns=SMB4-1.brockley.harte-lyne.ca., email=hostmaster.brockley.harte-lyne.ca. (flags=600000f0, serial=110, ttl=3600) NS:

FreeBSD-12.1p7 Samba-4.10.15 The user profiles were transferred from the existing Samba AD-DC to a new domain running on Samba-4.10. An ls on the original Samba (4.3.13) domain DC shows this: [root at SAMBA-01 ~]# ls -ld /var/samba4/BROCKLEY-2016/PROFILES/lyneak_hll.V2 drwxrwx---+ 16 BROCKLEY-2016\lyneak_hll BROCKLEY-2016\domain admins 512 Aug 12 17:07

I have a dc configured to use the samba internal dns service. The version of samba I am using is 4.10.15 packaged for FreeBSD. Its build options state this: BIND911 : off BIND916 : off , , , GSSAPI_BUILTIN : on GSSAPI_MIT : off LDAP : on . . . NSUPDATE : off My smb4.conf file contains this: [global] bind interfaces only = Yes dns forwarder =

FreeBSD-12.1p6 IOCage thick jails on ZFS, samba-4.10.15: On Fri, July 10, 2020 02:29, Andrea Venturoli wrote: > On 2020-07-09 21:36, James B. Byrne via samba wrote: >> set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_PARAMETER. >> ERROR(runtime): uncaught exception - (3221225485, 'An invalid parameter was >> passed to a service or function.') > > What

I am trying to get VSFTPD to listen on a particular IP. The ifconfig output for the host is: eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX inet addr:aaa.bbb.ccc.26 Bcast:aaa.bbb.ccc.255 Mask:255.255.255.0 inet6 addr: xxxx::xxx:xxx:xxxx:xxxx/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:223374 errors:0 dropped:0

On Sat, July 11, 2020 04:32, Andrea Venturoli wrote: > On 2020-07-10 14:47, James B. Byrne wrote: >> FreeBSD-12.1p6 IOCage thick jails on ZFS, samba-4.10.15: > > Can you post the smb.conf of both DCs? > > Just out of curiosity, are you also using vfs_zfsacl? Yes. smb.confs DC1 and DC2: /zroot/iocage/jails/smb4-1a/root/usr/local/etc/smb4.conf [root at vhost04 ~ (master)]#

On Wed, March 15, 2017 22:31, Andrew Walker wrote: > What does your smb.conf look like? Are you using ACLs? If so, post > 'getfacl' output for the problem directory (ie 'getfacl > /mnt/tank/foo'). > Thank you for your reply. Here is the requested information. getfacl /var/samba4/BROCKLEY-2016/PROFILES/byrnej.V2 # file: /var/samba4/BROCKLEY-2016/PROFILES/byrnej.V2 #

On the original AD DC I see this error: /usr/sbin/rndc: Failed to exec child - No such file or directory [2020/06/25 15:38:50.565496, 0] ../../source4/dsdb/dns/dns_update.c:91(dnsupdate_rndc_done) ../../source4/dsdb/dns/dns_update.c:90: Failed rndc update - NT_STATUS_UNSUCCESSFUL But there is no rndc program anywhere on this system. And internal DNS is all that was ever enabled.