similar to: DNS Zone Transfers are Enabled

Displaying 20 results from an estimated 10000 matches similar to: "DNS Zone Transfers are Enabled"

2019 Jul 22
1
DNS Zone Transfers are Enabled
Thanks Roland, You are correct. Our Bind9 DLZ is version 9.9.4. I'll have to check if I will be able to upgrade to a newer version of Bind, these are on our production servers. On Mon, Jul 22, 2019 at 9:40 AM Rowland penny via samba < samba at lists.samba.org> wrote: > On 22/07/2019 08:24, Eben Victor via samba wrote: > > Hello All, > > > > I hope someone might be
2018 Jul 30
8
Internal DNS migrate to Bind9_DLZ
Hello Rowland, See below as requested. /etc/named.conf # Global Configuration Options include "/var/lib/samba/bind-dns/named.conf"; options { dump-file "/var/named/data/cache_dump.db"; statistics-file "/var/named/data/named_stats.txt"; memstatistics-file "/var/named/data/named_mem_stats.txt"; auth-nxdomain yes; directory
2020 Feb 28
3
Samba Bind DLZ Slow queries
So if this is done, is edns configure also ? ? in resolv.conf add: options edns0 ? and, name.conf test these. ? ??????? //?The forwarded zone to the AD-DC DNS use these also. ????????//dnssec-must-be-secure?internal.domain.tld no; ????????//dnssec-must-be-secure 168.192.in-addr.arpa no; ????????// listen-on-v6 { ::1; };? // test what works best, if not all?ipv6 is disabled also?enable this
2018 Jul 30
4
Internal DNS migrate to Bind9_DLZ
It is part of the Sernet packages and is currently on 1.3.4 /usr/lib64/samba/libldb.so.1.3.4 We started using sernet-samba-ad from v4 using the internal dns and updated as versions were released. We have now recently updated from 4.8.2 to 4.8.3 and still using internal dns. Our DNS is working as it should, it's only been since recently that we have to migrate to bind9. On Mon, Jul 30, 2018
2020 Feb 28
4
Samba Bind DLZ Slow queries
Hello All, I hope you can assist me, I'm running Bind DLZ with our Samba AD DC environment Bind: BIND 9.11.4-P2-RedHat-9.11.4-9.P2.el7 (Extended Support Version) Samba: Version 4.11.6-SerNet-RedHat-9.el7 OS: Red Hat Enterprise Linux Server release 7.7 (Maipo) My DNS queries seems to be hanging intermittently, taking anything from 1sec - 15sec or even timing out. I'm been monitoring the
2020 Feb 28
4
Samba Bind DLZ Slow queries
Thanks Rowland, I have removed from options, and amended the forwarders. [global] workgroup = <MYDOMAIN> realm = <MYDOMAIN>.CORP netbios name = <HOSTNAME> server role = active directory domain controller idmap_ldb:use rfc2307 = yes idmap config * : range = 3000-7999 ----------> If I remove the portion I get errors -> idmap
2018 Jul 30
2
Internal DNS migrate to Bind9_DLZ
Yes I have added "server services = -dns" to my smb.conf file and also removed "dns forwarder =" I've done the same setup but on Samba 4.7.7, RHEL6, named 9.8 and this works perfect. On Mon, Jul 30, 2018 at 11:18 AM Rowland Penny via samba < samba at lists.samba.org> wrote: > On Mon, 30 Jul 2018 10:57:11 +0200 > Eben Victor <eben.victor at gmail.com>
2018 Oct 31
3
Internal DNS migrate to Bind9_DLZ
Hi Rowland, I didn't build samba, I'm running the sernet packages, # rpm -qa | grep sernet sernet-samba-libsmbclient0-4.8.6-16.el7.x86_64 sernet-samba-ad-4.8.6-16.el7.x86_64 sernet-samba-libs-4.8.6-16.el7.x86_64 sernet-samba-client-4.8.6-16.el7.x86_64 sernet-samba-winbind-4.8.6-16.el7.x86_64 sernet-samba-common-4.8.6-16.el7.x86_64 sernet-samba-4.8.6-16.el7.x86_64 I don't mind having
2018 Jul 30
2
Internal DNS migrate to Bind9_DLZ
Hello, I hope that someone can perhaps assist me or just guide me in the right direction. I've been following all the steps for setting up and migrating my Samba Internal DNS to Bind9_DLZ. https://wiki.samba.org/index.php/Setting_up_a_BIND_DNS_Server https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End But this doesn't seem to work for me, I can get bind started up 100% when I remove
2018 Jul 30
2
Internal DNS migrate to Bind9_DLZ
Hello Rowland, Please see below installed samba packages. # rpm -qa | grep samba sernet-samba-client-4.8.3-11.el7.x86_64 sernet-samba-common-4.8.3-11.el7.x86_64 sernet-samba-libsmbclient0-4.8.3-11.el7.x86_64 sernet-samba-4.8.3-11.el7.x86_64 sernet-samba-ad-4.8.3-11.el7.x86_64 sernet-samba-libs-4.8.3-11.el7.x86_64 sernet-samba-winbind-4.8.3-11.el7.x86_64 ldb is installed with the samba packages.
2018 Oct 31
2
Internal DNS migrate to Bind9_DLZ
Hello Rowland, I have already checked and the DN's are in AD, see attached. SOA: <domain>.corp. 3600 IN SOA psad102zadprh.<domain>.corp. . 9766 3600 600 86400 3600 See below NS, but the 1st NS (zatprdc001) doesn't exsit, and I cannot find it anywhere. NS: <domain>.corp. 3600 IN NS zatprdc001.<domain>.corp. <domain>.corp. 3600
2018 Oct 31
3
FW: Internal DNS migrate to Bind9_DLZ
Hai,   I've checked out the log you send and i re-read the complete thread.   Based on thats done and what i did see in you logs now, looks like a  * (wildcard)  entry is giving the problem. But i am not sure of that, the wildcard bugs should be fixed, when i look in bugzilla.  (#10435 #12952 )   I've forwarded the mail to Rowland also before we go throw things at you again. ;-)
2018 Jul 30
5
Internal DNS migrate to Bind9_DLZ
Hello Rowland, selinux has been disabled, I also ran th follow # systemctl stop sernet-samba-ad # samba_upgradedns --dns-backend=BIND9_DLZ # named -d3 -f -g -u named Which then still fails, see below smb.conf [global] workgroup = DOMAIN realm = DOMAIN.CORP netbios name = PDC server role = active directory domain controller idmap_ldb:use rfc2307 = yes
2019 Feb 26
1
samba internal DNS Zone transfers and notify for slaves?
I was wondering if I can implement slave DNS servers for a samba domain. I would like to setup a slave section on my bind server that gets its information from my samba-ad dns server? Or is my only option at the moment to use bind-dlz with bind on my samba-dc? This page: https://wiki.samba.org/index.php/DNS_Administration says zone transfers is unimplemented but one of the links on there
2020 Feb 28
0
Samba Bind DLZ Slow queries
Hai Eben (victor), ? Great to hear that, you opened TCP 53 ? edns?tcp/53?packet size 4096. dns??? udp/53 packet size 512? ? having that right helps?a lot, but only that is often not enough.? This is why i add the options also to resolv.conf and?bind.? ? test a bit, and see what works best for you. ? Great weekend. ? Greetz, ? Louis Van: Eben Victor [mailto:eben.victor at gmail.com]
2015 Sep 07
5
BIND DLZ zone transfers
I am looking at: https://wiki.samba.org/index.php/DNS_administration I am using bind 9.9 on all my DNS servers. To set up secondarying my Samba DNS zones to my other Bind servers. I come across the following: https://bugzilla.samba.org/show_bug.cgi?id=9634 Is it possible to transfer the DLZ zones now as dates on this bug are 2 years old?
2016 Apr 07
2
GPO
Hi Louis, See below,  C:\>ipconfig /all Windows IP Configuration    Host Name . . . . . . . . . . . . : EBEN-TEST-PC    Primary Dns Suffix  . . . . . . . : domain.corp    Node Type . . . . . . . . . . . . : Hybrid    IP Routing Enabled. . . . . . . . : No    WINS Proxy Enabled. . . . . . . . : No    DNS Suffix Search List. . . . . . : domain.corp Ethernet adapter Local Area Connection:
2018 Nov 01
5
Internal DNS migrate to Bind9_DLZ
Hai, > > > > have rejoined all my DC's with new names, see below. > >;; ANSWER SECTION: > ><domain>.corp. 3600 IN NS psad101zatcrh.<domain>.corp. -> New > >rebuild, new hostname, RHEL6 to RHEL7 upgrade .... > > > > Led me to believe this is your problem. However, you say it works on > > one DC, but not with multiple
2015 Sep 07
2
Maybe working - Re: BIND DLZ zone transfers
Hi Robert, yes it does work. But the DLZ bind will not notify any slaves, when the repository changes. This can be painful, especially for longer TTL values. Regards, - lars. Am 07.09.2015 um 20:16 schrieb Robert Moskowitz: > > > On 09/07/2015 12:52 PM, Robert Moskowitz wrote: >> I am looking at: https://wiki.samba.org/index.php/DNS_administration >> >> I am using
2016 Apr 06
1
GPO
Any event id for this one? If its event id : 1110. Open CMD box, type ipconfig /all And post the result. I suppect one of the following. 1) pc cloned without sysprep, so multiple pc's with same SID. 2) wrong DNS-Domain suffix 3) wrong DNS-Search suffix Test this by remove you pc from domain, add it again, reboot. Login with the same user. Greetz, Louis >