Hai, I suggest you dont remove the "Register DNS" checkbox from the network" option. If you setup if correct, when you join a computer to the domain, It wil automatily registere the computer en the AD DNS. And todo so you need the "Register DNS" checkbox from the network" For example, i use for now an dhcp server ! the DHCP server i use it NOT in any of the MS domains and/or Samba AD ! So its just a dhcp server, not linked to any domain. And i have 3 MS domains here. If i join the domain with an pc with dhcp ip, it is registered as it should. And same with pc's that have a dedicated IP. So, or the dhcp server is giving the wrong options to the pc. or your missing the reverse DNS zone. This should work out of the box, without any registry modification etc.. Greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Viktor Trojanovic > Verzonden: maandag 16 november 2015 10:47 > Aan: Rowland Penny; samba at lists.samba.org > Onderwerp: Re: [Samba] Win Clients and DNS > > > > On 16.11.2015 09:57, Rowland Penny wrote: > > On 16/11/15 00:31, Viktor Trojanovic wrote: > >> I have an AD with 1 Samba DC and 5 Windows 10 clients. The DC and the > >> clients all have a fixed IPv4 address. > >> > >> In the windows event viewer, I constantly see the following warning: > >> > >> Event 8019, DNS Client Events > >> ------------------------------------------ > >> The system failed to register host (A or AAA) resource records (RRs) > >> for network adapter with settings: > >> > >> Adapter Name: {someGUID} > >> Host Name: Client-PC > >> Primary Domain Suffix: SAMDOM.COM > >> DNS Server list: > >> 192.168.0.1 > >> Sent update to server: <?> > >> IP Addresses: > >> 192.168.0.15 > >> ------------------------------------------ > >> > >> Is it necessary to manually make some entries in DNS for the client > >> machines? I didn't see anything about that in the Wiki. > >> > >> I'm trying to figure out if this is connected to another problem I'm > >> facing. A machine based GPO is not executed because "the file > >> \\SAMDOM.COM\SysVol\[...]\gpt.ini from a domain controller could not > >> be read", and as one of the possible reasons for the error, name > >> resolution is mentioned. I can access the file just fine once I'm > >> logged in so I really don't know what the issue is here. > >> > >> Thanks, > >> Viktor > >> > > > > Is there anything in syslog on the DC, it may be that whilst your > > clients are trying to update their dns records in AD, they are being > > denied. > > If the clients were Unix based, you would have to add their records to > > AD manually, It is probably the same for fixed window clients. > > There is something on the wiki about adding dns records, but it is a > > bit unclear as to why you would need to do this: > > > > https://wiki.samba.org/index.php/DNS_administration#Adding_new_records > > > > Rowland > > Yes, I read that, and I'm not clear either on why the clients need > registration and what the disadvantages would be if they aren't. But > Ole's tip to remove the "Register DNS" checkbox from the network > interface on Win Clients does seem like valuable information for the wiki. > > Viktor > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
Hi Louis, I don't use DHCP so most of what you wrote doesn't apply in my case. As for the reverse zone: I followed the wiki in this respect and do have a reverse lookup zone for the network, pointing to the DC. RLZ: 0.168.192.in-addr.arpa PTR 192.168.0.1 NS dc samdom.com SOA [2], dc.samdom.com, hostmaster.samdom.com Let me know if you see any issues in this configuration, thanks. Viktor On 16.11.2015 11:41, L.P.H. van Belle wrote:> Hai, > > I suggest you dont remove the "Register DNS" checkbox from the network" option. > > If you setup if correct, when you join a computer to the domain, > It wil automatily registere the computer en the AD DNS. > And todo so you need the "Register DNS" checkbox from the network" > > For example, i use for now an dhcp server > ! the DHCP server i use it NOT in any of the MS domains and/or Samba AD ! > So its just a dhcp server, not linked to any domain. > And i have 3 MS domains here. > > If i join the domain with an pc with dhcp ip, it is registered as it should. > And same with pc's that have a dedicated IP. > > So, > or the dhcp server is giving the wrong options to the pc. > or your missing the reverse DNS zone. > > This should work out of the box, without any registry modification etc.. > > Greetz, > > Louis > > > >> -----Oorspronkelijk bericht----- >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Viktor Trojanovic >> Verzonden: maandag 16 november 2015 10:47 >> Aan: Rowland Penny; samba at lists.samba.org >> Onderwerp: Re: [Samba] Win Clients and DNS >> >> >> >> On 16.11.2015 09:57, Rowland Penny wrote: >>> On 16/11/15 00:31, Viktor Trojanovic wrote: >>>> I have an AD with 1 Samba DC and 5 Windows 10 clients. The DC and the >>>> clients all have a fixed IPv4 address. >>>> >>>> In the windows event viewer, I constantly see the following warning: >>>> >>>> Event 8019, DNS Client Events >>>> ------------------------------------------ >>>> The system failed to register host (A or AAA) resource records (RRs) >>>> for network adapter with settings: >>>> >>>> Adapter Name: {someGUID} >>>> Host Name: Client-PC >>>> Primary Domain Suffix: SAMDOM.COM >>>> DNS Server list: >>>> 192.168.0.1 >>>> Sent update to server: <?> >>>> IP Addresses: >>>> 192.168.0.15 >>>> ------------------------------------------ >>>> >>>> Is it necessary to manually make some entries in DNS for the client >>>> machines? I didn't see anything about that in the Wiki. >>>> >>>> I'm trying to figure out if this is connected to another problem I'm >>>> facing. A machine based GPO is not executed because "the file >>>> \\SAMDOM.COM\SysVol\[...]\gpt.ini from a domain controller could not >>>> be read", and as one of the possible reasons for the error, name >>>> resolution is mentioned. I can access the file just fine once I'm >>>> logged in so I really don't know what the issue is here. >>>> >>>> Thanks, >>>> Viktor >>>> >>> Is there anything in syslog on the DC, it may be that whilst your >>> clients are trying to update their dns records in AD, they are being >>> denied. >>> If the clients were Unix based, you would have to add their records to >>> AD manually, It is probably the same for fixed window clients. >>> There is something on the wiki about adding dns records, but it is a >>> bit unclear as to why you would need to do this: >>> >>> https://wiki.samba.org/index.php/DNS_administration#Adding_new_records >>> >>> Rowland >> Yes, I read that, and I'm not clear either on why the clients need >> registration and what the disadvantages would be if they aren't. But >> Ole's tip to remove the "Register DNS" checkbox from the network >> interface on Win Clients does seem like valuable information for the wiki. >> >> Viktor >> >> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba > >
More explained.. Only my laptops get a DHCP IP. All my other computers have static ip. After the AD join, it does not matter if 1) a desktop pc, when a static IP changes for a computer. 2) a laptop gets a different IP. The PC always updates its A and PTR So, in both cases my A and PTR records are changed in the DNS. Maybe an firewall setting on you pc is blocking the update to the dns server or on the server you now allowing the dns updates. Can you have a look into that? Greetz, Louis> -----Oorspronkelijk bericht----- > Van: Viktor Trojanovic [mailto:viktor at troja.ch] > Verzonden: maandag 16 november 2015 12:02 > Aan: L.P.H. van Belle; samba at lists.samba.org > Onderwerp: Re: [Samba] Win Clients and DNS > > Hi Louis, > > I don't use DHCP so most of what you wrote doesn't apply in my case. > > As for the reverse zone: I followed the wiki in this respect and do have > a reverse lookup zone for the network, pointing to the DC. > > RLZ: 0.168.192.in-addr.arpa > PTR 192.168.0.1 > NS dc samdom.com > SOA [2], dc.samdom.com, hostmaster.samdom.com > > Let me know if you see any issues in this configuration, thanks. > > Viktor > > On 16.11.2015 11:41, L.P.H. van Belle wrote: > > Hai, > > > > I suggest you dont remove the "Register DNS" checkbox from the network" > option. > > > > If you setup if correct, when you join a computer to the domain, > > It wil automatily registere the computer en the AD DNS. > > And todo so you need the "Register DNS" checkbox from the network" > > > > For example, i use for now an dhcp server > > ! the DHCP server i use it NOT in any of the MS domains and/or Samba AD > ! > > So its just a dhcp server, not linked to any domain. > > And i have 3 MS domains here. > > > > If i join the domain with an pc with dhcp ip, it is registered as it > should. > > And same with pc's that have a dedicated IP. > > > > So, > > or the dhcp server is giving the wrong options to the pc. > > or your missing the reverse DNS zone. > > > > This should work out of the box, without any registry modification etc.. > > > > Greetz, > > > > Louis > > > > > > > >> -----Oorspronkelijk bericht----- > >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Viktor > Trojanovic > >> Verzonden: maandag 16 november 2015 10:47 > >> Aan: Rowland Penny; samba at lists.samba.org > >> Onderwerp: Re: [Samba] Win Clients and DNS > >> > >> > >> > >> On 16.11.2015 09:57, Rowland Penny wrote: > >>> On 16/11/15 00:31, Viktor Trojanovic wrote: > >>>> I have an AD with 1 Samba DC and 5 Windows 10 clients. The DC and the > >>>> clients all have a fixed IPv4 address. > >>>> > >>>> In the windows event viewer, I constantly see the following warning: > >>>> > >>>> Event 8019, DNS Client Events > >>>> ------------------------------------------ > >>>> The system failed to register host (A or AAA) resource records (RRs) > >>>> for network adapter with settings: > >>>> > >>>> Adapter Name: {someGUID} > >>>> Host Name: Client-PC > >>>> Primary Domain Suffix: SAMDOM.COM > >>>> DNS Server list: > >>>> 192.168.0.1 > >>>> Sent update to server: <?> > >>>> IP Addresses: > >>>> 192.168.0.15 > >>>> ------------------------------------------ > >>>> > >>>> Is it necessary to manually make some entries in DNS for the client > >>>> machines? I didn't see anything about that in the Wiki. > >>>> > >>>> I'm trying to figure out if this is connected to another problem I'm > >>>> facing. A machine based GPO is not executed because "the file > >>>> \\SAMDOM.COM\SysVol\[...]\gpt.ini from a domain controller could not > >>>> be read", and as one of the possible reasons for the error, name > >>>> resolution is mentioned. I can access the file just fine once I'm > >>>> logged in so I really don't know what the issue is here. > >>>> > >>>> Thanks, > >>>> Viktor > >>>> > >>> Is there anything in syslog on the DC, it may be that whilst your > >>> clients are trying to update their dns records in AD, they are being > >>> denied. > >>> If the clients were Unix based, you would have to add their records to > >>> AD manually, It is probably the same for fixed window clients. > >>> There is something on the wiki about adding dns records, but it is a > >>> bit unclear as to why you would need to do this: > >>> > >>> https://wiki.samba.org/index.php/DNS_administration#Adding_new_records > >>> > >>> Rowland > >> Yes, I read that, and I'm not clear either on why the clients need > >> registration and what the disadvantages would be if they aren't. But > >> Ole's tip to remove the "Register DNS" checkbox from the network > >> interface on Win Clients does seem like valuable information for the > wiki. > >> > >> Viktor > >> > >> > >> -- > >> To unsubscribe from this list go to the following URL and read the > >> instructions: https://lists.samba.org/mailman/options/samba > > > >
On 16.11.2015 14:22, L.P.H. van Belle wrote:> More explained.. > > Only my laptops get a DHCP IP. > All my other computers have static ip. > > After the AD join, it does not matter if > 1) a desktop pc, when a static IP changes for a computer. > 2) a laptop gets a different IP. > The PC always updates its A and PTR > > So, in both cases my A and PTR records are changed in the DNS. > > Maybe an firewall setting on you pc is blocking the update to the dns server or on the server you now allowing the dns updates. > > Can you have a look into that? > > Greetz, > > Louis >OK, so my situation is as follow: - NDS A and PTR are manually set on the Samba DNS for all domain members - All clients have fixed IP addresses and are in the same subnet as the Samba server - I disabled the Windows Firewall just to make sure there is no block on the PC either ==> No change, I still get the same error message in the windows event viewer. If I look at the error message, one line which seems wrong is ----> Sent update to server: <?> It does give the correct IP address in the following line but is this how it should look? Viktor> > > > > >> -----Oorspronkelijk bericht----- >> Van: Viktor Trojanovic [mailto:viktor at troja.ch] >> Verzonden: maandag 16 november 2015 12:02 >> Aan: L.P.H. van Belle; samba at lists.samba.org >> Onderwerp: Re: [Samba] Win Clients and DNS >> >> Hi Louis, >> >> I don't use DHCP so most of what you wrote doesn't apply in my case. >> >> As for the reverse zone: I followed the wiki in this respect and do have >> a reverse lookup zone for the network, pointing to the DC. >> >> RLZ: 0.168.192.in-addr.arpa >> PTR 192.168.0.1 >> NS dc samdom.com >> SOA [2], dc.samdom.com, hostmaster.samdom.com >> >> Let me know if you see any issues in this configuration, thanks. >> >> Viktor >> >> On 16.11.2015 11:41, L.P.H. van Belle wrote: >>> Hai, >>> >>> I suggest you dont remove the "Register DNS" checkbox from the network" >> option. >>> If you setup if correct, when you join a computer to the domain, >>> It wil automatily registere the computer en the AD DNS. >>> And todo so you need the "Register DNS" checkbox from the network" >>> >>> For example, i use for now an dhcp server >>> ! the DHCP server i use it NOT in any of the MS domains and/or Samba AD >> ! >>> So its just a dhcp server, not linked to any domain. >>> And i have 3 MS domains here. >>> >>> If i join the domain with an pc with dhcp ip, it is registered as it >> should. >>> And same with pc's that have a dedicated IP. >>> >>> So, >>> or the dhcp server is giving the wrong options to the pc. >>> or your missing the reverse DNS zone. >>> >>> This should work out of the box, without any registry modification etc.. >>> >>> Greetz, >>> >>> Louis >>> >>> >>> >>>> -----Oorspronkelijk bericht----- >>>> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Viktor >> Trojanovic >>>> Verzonden: maandag 16 november 2015 10:47 >>>> Aan: Rowland Penny; samba at lists.samba.org >>>> Onderwerp: Re: [Samba] Win Clients and DNS >>>> >>>> >>>> >>>> On 16.11.2015 09:57, Rowland Penny wrote: >>>>> On 16/11/15 00:31, Viktor Trojanovic wrote: >>>>>> I have an AD with 1 Samba DC and 5 Windows 10 clients. The DC and the >>>>>> clients all have a fixed IPv4 address. >>>>>> >>>>>> In the windows event viewer, I constantly see the following warning: >>>>>> >>>>>> Event 8019, DNS Client Events >>>>>> ------------------------------------------ >>>>>> The system failed to register host (A or AAA) resource records (RRs) >>>>>> for network adapter with settings: >>>>>> >>>>>> Adapter Name: {someGUID} >>>>>> Host Name: Client-PC >>>>>> Primary Domain Suffix: SAMDOM.COM >>>>>> DNS Server list: >>>>>> 192.168.0.1 >>>>>> Sent update to server: <?> >>>>>> IP Addresses: >>>>>> 192.168.0.15 >>>>>> ------------------------------------------ >>>>>> >>>>>> Is it necessary to manually make some entries in DNS for the client >>>>>> machines? I didn't see anything about that in the Wiki. >>>>>> >>>>>> I'm trying to figure out if this is connected to another problem I'm >>>>>> facing. A machine based GPO is not executed because "the file >>>>>> \\SAMDOM.COM\SysVol\[...]\gpt.ini from a domain controller could not >>>>>> be read", and as one of the possible reasons for the error, name >>>>>> resolution is mentioned. I can access the file just fine once I'm >>>>>> logged in so I really don't know what the issue is here. >>>>>> >>>>>> Thanks, >>>>>> Viktor >>>>>> >>>>> Is there anything in syslog on the DC, it may be that whilst your >>>>> clients are trying to update their dns records in AD, they are being >>>>> denied. >>>>> If the clients were Unix based, you would have to add their records to >>>>> AD manually, It is probably the same for fixed window clients. >>>>> There is something on the wiki about adding dns records, but it is a >>>>> bit unclear as to why you would need to do this: >>>>> >>>>> https://wiki.samba.org/index.php/DNS_administration#Adding_new_records >>>>> >>>>> Rowland >>>> Yes, I read that, and I'm not clear either on why the clients need >>>> registration and what the disadvantages would be if they aren't. But >>>> Ole's tip to remove the "Register DNS" checkbox from the network >>>> interface on Win Clients does seem like valuable information for the >> wiki. >>>> Viktor >>>> >>>> >>>> -- >>>> To unsubscribe from this list go to the following URL and read the >>>> instructions: https://lists.samba.org/mailman/options/samba >>> > >