Bind updating root hint data file racemization dating definition
Thank you and best regards, Torsten -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba A quick search on Google gives: Best regards, Marcel de Reuver 2017-06-06 GMT Torsten Kurbad via samba The OP basically did that manually, but it didn't change the record in AD. Seeing which aliases work against Windows would be a good idea ('.' is what Samba supports for modification but is supplying '.. Cheers, Garming On 07/06/17 , Rowland Penny via samba wrote: valid against Windows or for which calls. (Last part is German - Unfortunately, I don't have an English Windows version at my disposal, but loosely translated it would be something like "The name could not be found".) Thus, my question is: What is the correct way to update Samba's root hints? Any tests of Root Hints in python/samba/tests/samba_tool/would be appreciated. I'm also not sure if users of the correct permission will be able (or unable) to modify this zone. The record has this DN: DC=h.root-servers.net, DC=Root DNSServers, CN=Microsoft DNS, DC=Domain Dns Zones, DC=samdom, DC=example, DC=com So the zone seems to be 'Root DNSServers' but this doesn't seem to exist :-( Rowland -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba Exactly. The object in AD for 'Root DNSServers' looks like a zone record, it is in 'CN=Microsoft DNS, DC=Domain Dns Zones, DC=samdom, DC=example, DC=com' and it has the 'object Class' dns Zone, therefore it is a zone. The record is an 'A' record, but 'samba-tool dns update' will not change it, because it claims the zone does not exist. The zone is definitely called 'Root DNSServers' not '.' If something looks like a duck, walks like a duck and quacks like a duck, it is a duck.In fact, these two latter servers will ever be referred to in the configuration because the xxxbox will be in charge of resolving names if the packet destination isn't known.Consequently, I consider the xxxbox like a primary server outside of our domain.Putting a DNS server on a network allows for the replacement of IP addresses of individual machines by a name.
It looks like the 'C' code is where the problem lies.
For example, pop.example.com, could both point to the primary server where the mail server and the business intranet reside, and the domain could be
It's easy to remember that these two services are running on the same machine whose IP address is 192.168.0.1.
Thus, such a manual change would be error prone, to say the least. What is the difference between: DC=devstation, DC=samdom.example.com, CN=Microsoft DNS, DC=Domain Dns Zones, DC=samdom, DC=example, DC=com and DC=h.root-servers.net, DC=Root DNSServers, CN=Microsoft DNS, CN=System, DC=samdom, DC=example, DC=com The difference is that you can update the first record, but you cannot update the second, even though they are both valid DNS records in a zone.
Of course, I could try and change the data using ldbedit, but AD DNS records are stored in a binary encoded data structure that not only includes record type and value, but also a serial number, etc. Samba needs to see this zone before we can even think about updating/changing the root records.