search for: bind99

...penny wrote: (I understand this might be specific to FreeBSD, but I asked on its mailing list and got no answer...) >> Then why is it an option *in alternative* to BIND? > > What do you mean '*in alternative*' ?? I mean when I build Samba port, I can choose NSUPDATE *or* BIND99 *or* BIN910 (where "or" means "exclusive or", I can choose at most one). Those options are described as: BIND99 = Use bind99 as AD DC DNS server frontend BIND910 = Use bind910 as AD DC DNS server frontend NSUPDATE = Use samba NSUPDATE utility for AD DC Notice this options onl...

...ific to FreeBSD, but I asked on its > mailing list and got no answer...) > > > > > >>> Then why is it an option *in alternative* to BIND? >> >> What do you mean '*in alternative*' ?? > > I mean when I build Samba port, I can choose NSUPDATE *or* BIND99 *or* > BIN910 (where "or" means "exclusive or", I can choose at most one). > > Those options are described as: > BIND99 = Use bind99 as AD DC DNS server frontend > BIND910 = Use bind910 as AD DC DNS server frontend OK, these are just what version of bind to use....

On 05/03/16 22:55, Rowland penny wrote: > Don't use freebsd, but Samba 4, when run as an AD DC, uses nsupdate to > update a computers DNS records in AD. First off, thanks for answering. Alas, I don't really understand what you mean... Is it used to dynamically add A records for clients that connect to the AD? >> Is it intended to work with BIND (like the other two in

...SYSLOG=on: Syslog support UTMP=on: UTMP accounting support WINBIND=on: WinBIND support ====> Options available for the single DNS: you have to select exactly one of them NSUPDATE=off: Use internal DNS with NSUPDATE utility BIND98=off: Use bind98 as a DNS server frontend BIND99=on: Use bind99 as a DNS server frontend ====================================================================================================== Now i want to rebuild Samba from tarball with an options --with-acl-support (default=yes) --with-aio-support (default=yes) --enable-avahi (default=yes...

...or code 1 Stop in /usr/local/samba-master. root at hq:/usr/local/samba-master # root at hq:/usr/local/samba-master # uname -a FreeBSD hq.pccom.ca 9.2-STABLE FreeBSD 9.2-STABLE #7: Fri Oct 4 19:00:49 EDT 2013 root at pccom.ca:/usr/obj/usr/src/sys/frank amd64 Samba4.0.12 from port works with Bind99. Any one can help? Tell me how I can help? Thanks!

...SYSLOG=on: Syslog support UTMP=on: UTMP accounting support WINBIND=on: WinBIND support ====> Options available for the single DNS: you have to select exactly one of them NSUPDATE=off: Use internal DNS with NSUPDATE utility BIND98=off: Use bind98 as a DNS server frontend BIND99=on: Use bind99 as a DNS server frontend =============================================================== My named.conf acl "mynet" { 192.168.0.0/28; 127.0.0.1; }; options { #include "/var/db/samba4/private/named.conf"; #Both files are integrated here, to easy for me...

...am-krb5 > libnss-winbind krb5-config krb5-user ntp dnsutils ldb-tools bind9 > bind9utils > > of course fedora would have all different package names. I avoided installing bind-chroot and bind-sdb-chroot.x86_64 as the bind dlz info on samba said not to chroot bind I'm not sure what bind99 libs are but I installed all other bind packages listed with "dnf list bind*" [root at dc1 ~]# dnf list dns* |grep -v i686 Last metadata expiration check: 2:40:26 ago on Mon 10 Jul 2017 05:51:50 AM MDT. Installed Packages dnsjava.noarch 2.1.3-12.fc26 @rawhide...

...tp dnsutils ldb-tools bind9 >>> bind9utils >>> >>> of course fedora would have all different package names. >> I avoided installing bind-chroot and bind-sdb-chroot.x86_64 as the bind >> dlz info on samba >> said not to chroot bind I'm not sure what bind99 libs are but I installed >> all other bind >> packages listed with "dnf list bind*" >> >> [root at dc1 ~]# dnf list dns* |grep -v i686 >> Last metadata expiration check: 2:40:26 ago on Mon 10 Jul 2017 05:51:50 >> AM MDT. >> Installed Packages >...

...bind9utils >>>>> >>>>> of course fedora would have all different package names. >>>> I avoided installing bind-chroot and bind-sdb-chroot.x86_64 as the >>>> bind dlz info on samba >>>> said not to chroot bind I'm not sure what bind99 libs are but I >>>> installed all other bind >>>> packages listed with "dnf list bind*" >>>> >>>> [root at dc1 ~]# dnf list dns* |grep -v i686 >>>> Last metadata expiration check: 2:40:26 ago on Mon 10 Jul 2017 05:51:50 >>&...

...------------------------------ DNS ----------------------------------| | | | (*) NSUPDATE Use internal DNS with NSUPDATE utility | | | | ( ) BIND98 Use bind98 as a DNS server frontend | | | | ( ) BIND99 Use bind99 as a DNS server frontend | | | |--------------------------------- ZEROCONF -------------------------------| | | | ( ) AVAHI Zeroconf support via Avahi | | | | (*) MDNSRE...

...krb5-config krb5-user ntp dnsutils ldb-tools bind9 >> bind9utils >> >> of course fedora would have all different package names. > I avoided installing bind-chroot and bind-sdb-chroot.x86_64 as the bind > dlz info on samba > said not to chroot bind I'm not sure what bind99 libs are but I installed > all other bind > packages listed with "dnf list bind*" > > [root at dc1 ~]# dnf list dns* |grep -v i686 > Last metadata expiration check: 2:40:26 ago on Mon 10 Jul 2017 05:51:50 AM > MDT. > Installed Packages > dnsjava.noarch...

...nd9 >>>> bind9utils >>>> >>>> of course fedora would have all different package names. >>> I avoided installing bind-chroot and bind-sdb-chroot.x86_64 as the bind >>> dlz info on samba >>> said not to chroot bind I'm not sure what bind99 libs are but I >>> installed all other bind >>> packages listed with "dnf list bind*" >>> >>> [root at dc1 ~]# dnf list dns* |grep -v i686 >>> Last metadata expiration check: 2:40:26 ago on Mon 10 Jul 2017 05:51:50 >>> AM MDT. >>...

...>>>> >>>>>> of course fedora would have all different package names. >>>>> I avoided installing bind-chroot and bind-sdb-chroot.x86_64 as the >>>>> bind dlz info on samba >>>>> said not to chroot bind I'm not sure what bind99 libs are but I >>>>> installed all other bind >>>>> packages listed with "dnf list bind*" >>>>> >>>>> [root at dc1 ~]# dnf list dns* |grep -v i686 >>>>> Last metadata expiration check: 2:40:26 ago on Mon 10 Jul 201...

Bind-9.11 is installed. How do you configure it? Does it need anything special in the config for samba to build the ...samba.../named.conf file that I should be able to include in my /etc/named.conf afterwards? My guess is that some directory is missing. But if I start fresh and configure samba with the internal dns it gets all the way through it's configuration with no errors. I've

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 Thanks: Tomáš Golembiovský --- v2v/virt-v2v.pod | 38 ++++++++++++++++++++++++++------------ 1 file changed, 26 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..0943bf305 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,32 @@ that

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 --- v2v/virt-v2v.pod | 39 +++++++++++++++++++++++++++------------ 1 file changed, 27 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..93d1a9ecd 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,33 @@ that guest through the RHV-M UI,

If the connection is not local, paths of disks will refer to the remote host, which were mistakenly handled as local paths (in the best case failing to open a non-existing disk, and in the worst case opening a different disk!). In case the disks are remote resources like ssh or ceph, nothing guarantees that the hostname can be reached from the local machine, or even that it is actually the same on

Hopefully this time ...