similar to: Ubuntu Linux Domain Member - FQDN works but hostname does not

Hi Paully I can help with showing the "subgroup" 0: instead of @ use 0 samba-tool dns query dc3 130.130.in-addr.arpa 0 ALL the additional 0 might be a bug in 4.7, which is end of life; I would suggest to upgrade first......but Rowland will know more about it probably. br Mani On 03.11.2020 11:24, Paul Littlefield via samba wrote: > Hello Samba List, > > I have 2 problems

Joining member Centos 7.8 Linux server with 4.10.4-10.el7 or higher appears to ignore client FQDN when AD domain does not match client domain name.? For example Active Directory Domain is ad1.testdomain.com and the client member server FQDN is? testhost.clients.testdomain.com.? When joining the domain? DNSHostName attribute in AD shows testhost.ad1.testdomain.com when it should be

Connecting to \\server.domain.xx.uk\share and \\server\share, works but we tend to lose "\\server\share" within a few days, *but starts working again*. \\FQDN\share eventually stops, with windows reporting "network path not found". If I do a "net use" I can see several connections to \\fqdn\share, and running "net use * /delete", brings back the the ability

Unless it's _not_ a global catalog. Check your SRV records again, there should be corresponding "_gc" records (similar to "_ldap") for each DC. So, based upon the link/graphic I posted earlier: * either your 2nd DC isn't being returned as a part of DNS lookups * or that 2nd DC isn't responding to queries for authentication * or the client isn't

On Fri, 11 Jan 2019 14:55:08 +0100 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > > > > > > > Please, does somebody have a clue, what goes wrong here? > > > > > > > > > > > > > Nope, haven't got a clue ;-) > Not? Rowland not? really.. ;-) Well okay, I could take a guess, but I could be wide

Hello Samba List, I have 2 problems with dns - seeing the child entries and a zone with an extra octet. First... I have created a /16 reverse zone as per the wiki page (https://wiki.samba.org/index.php/DNS_Administration#To_create_a_.2F24_reverse_zone)... $ samba-tool dns zonecreate dc3 130.130.in-addr.arpa $ samba-tool dns zonelist --reverse dc3 pszZoneName :

On Wed, 20 Feb 2019 11:17:05 +0100 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Hai, > > > -----Oorspronkelijk bericht----- > > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Mgr. > > Peter Tuharsky via samba > > Verzonden: woensdag 20 februari 2019 10:28 > > Aan: samba at lists.samba.org > > Onderwerp:

On 01/02/2020 15:10, Rowland penny via samba wrote: > Not really, all Samba AD DC's are global catalogs ;-) Ah, OK... so we don't need to worry about that then? -- Paul Littlefield Telephone: 07801 125705 Email: info at paully.co.uk Wiki: http://wiki.indie-it.com/wiki/Special:AllPages LinkedIn: https://www.linkedin.com/in/paullittlefield Paul Littlefield is environmentally

just a suggestion.. get www.xenserver.org install a xen server. get xen convertion tools. http://www.citrix.nl/downloads/xenserver/tools/conversion.html and migrate the linux on hardware box to Xen server. from here you can also export to OVF/OVA package or XVA file. the OVF can be inported in virtual box.. but i do everything with xen server. greetz, Louis

Hi, I have several machines running CentOS 6.2 and a strange problem with the hostname of one machine... After every reboot it loses the fqdn hostname. Here is my confguration: ifconfig | grep "inet addr" inet addr:10.0.0.12 Bcast:10.0.0.255 Mask:255.255.255.0 inet addr:127.0.0.1 Mask:255.0.0.0 /etc/sysconfig/network NETWORKING=yes HOSTNAME=x800.mydomain.local

>It isn't running, one of the first things I do when setting up a new DC is to remove nscd if it is installed. Ah ok... well this isn't a DC, just a member... is NSCD ok to run as a member? Otherwise I can remove it. > you get a caching dnsmasq server as standard Not on ubuntu server... There is no dnsmasq package installed nor is it in ps -ef > If you have to have that

> > > > Please, does somebody have a clue, what goes wrong here? > > > > > > > > Nope, haven't got a clue ;-) Not? Rowland not? really.. ;-) I'm a gambler so here you go ;-) Hmm, first 3 guesses.. Typos in primary DNS/Search domain. ( /etc/resolv.conf ) Typos in /etc/hosts Why. Ping host works ( host file ) ip host.fqdn host Ping host.fqdn

Rowland, thank You, but this removes only the NS record, but the faulty domain A records remain. How to deal with them, I don't know. They behave unlike the ordinary A records. Name=, Records=8, Children=0     SOA: serial=27, refresh=900, retry=600, expire=86400, minttl=3600, ns=blacktux.interbronz.local., email=hostmaster.interbronz.local. (flags=600000f0, serial=27, ttl=3600)     NS:

On 09/03/18 13:30, lingpanda101 via samba wrote: > On 3/9/2018 5:30 AM, Paul Littlefield via samba wrote: >> For some reason, the provision picked up 2 network IP addresses in my VM. >> >> Snipped output below... >> >> >> root at dc1.example.com ~ $ (screen) samba-tool dns serverinfo dc1 >>   dwVersion                   : 0xece0205 >>  

Well, finally I found the recommendations against .local here: https://wiki.samba.org/index.php/Active_Directory_Naming_FAQ However, still, the originating wiki should AFAIK be more verbose. https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller For now it only says "Make sure that you provision the AD using a DNS domain that will not need to be

Hm, I thought this to be the very TLD that is specifically assigned for local networks with no plans to become Internet-wide. What is the recommended TLD for such networks then? Dňa 20. 2. 2019 o 11:33 Rowland Penny via samba napísal(a): > On Wed, 20 Feb 2019 11:17:05 +0100 > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > >> Hai, >>

So everything with the hostname with now resolving correctly, without the 127.0.1.1 hack anymore. We just had to make sure DHCP was handing out the correct domain, which it is now: $ hostname -d windows.corp.XXX.com $ hostname -f freeradius.windows.corp.XXX.com I deleted all the shared secrets, removed the computer from AD and rejoined... but of course, we're still getting the exact same

Hi Gavin and I appear to have successfully connected our Linux and Windows machines via Tinc, but cannot seem to do anything else. We cannot ping each other's vpn network. Gavin would like to be able to: * browse my local SMB (Windows and Samba) network * collect his email via my local mail server Are asking too much of a VPN here? Have we missed something? All details, Linux output and

On 26/01/15 15:16, Paul Littlefield wrote: > On 26/01/15 15:08, Rowland Penny wrote: >> Yes, set up a new DC with your new OS and join this to the domain, >> once up and running, transfer the seven (yes, there are 7) FSMO roles >> to the new DC. Once everything is running ok, turn off the old DC and >> remove *all* mention of it from the domain. > > Hi Rowland

Sorry Paully, I thought i already replied it. The configs look good. Did a look back in time.. And Ahh.. Now this i missed. * yesterday, we changed the IP addresses of our DCs and the Wiki page did not mention (IMHO) 2 critical things... ... So you even missed more. Review all DNS entries for the problem DC and review your AD again. rgrep /etc and /var for all the old ip numbers and/or