similar to: Windows clients keep losing connections (FQDN and hostname)

Its littered throughout the docs eg.. https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs At best its *poor practice* which should not be frowned upon, but it just shows a real disconnect with real world users and systems, where admins are not "Domain Admins".

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

> > > > 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:

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: Re: [Samba] Samba + BIND9 DLZ. DNS dosen't resolve > FQDN, only short hostname > > Well, the mystery is solved. It WAS Avahi, in a way...

So, looks like the latest facter has fqdn... cool. but for some reason templates can''t access it. I was defining $fqdn in my site.pp, but had to remove it after the last yum update, which brought in a new facter package. But now my templates can use fqdn. Why would this happen? --jason

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

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

We have joined an Ubuntu Linux VM to the domain and will be using it for some basic shares. I can connect to it only in WINDOWS if I use its FQDN but not the netbios hostname of 'SERVER3'. It is listed in the DC AD. DNS forward and reverse lookups work for both just hostname and fqdn. What have I missed? -- Paul Littlefield

Rowland, thank You for advice. I can manage standard A records, but not sure, what to do with the NS. I can't figure out, how to delete invalid A subrecord of NS record. I'm afraid to experiment much. Please, could You point me to some working example? Peter Dňa 12. 1. 2019 o 15:00 Rowland Penny via samba napísal(a): > On Sat, 12 Jan 2019 10:35:59 +0100 > Peter Tuharsky via

Hi All. I am using: #rpm -qa | egrep ''puppet|facter'' puppetlabs-release-6-7.noarch puppet-3.1.1-1.el6.noarch facter-1.7.1-1.el6.x86_64 on: #cat /etc/redhat-release ; uname -r CentOS release 6.4 (Final) 2.6.32-358.11.1.el6.centos.plus.x86_64 My hostname is server.one.two.com: # hostname server.one.two.com # hostname --fqdn one.two.com #grep HOSTNAME /etc/sysconfig/network

Greets, samba-users, I contact this list because of a problem I face at a customer's site. We run Samba version 3.0.28-0.6-1787-SUSE-CODE10 there on a SLES 10 SP2 server. This server is located behind a firewall (run by me), that firewall allows all relevant Samba-ports through (137-139, 445). The clients are located in a separated subnet, the routing between client- and server-subnet is

I''ve begun using Hiera in combination with Foreman, primarily storing data that is best left in Array/Hash form. I''d like to be able to have a module, in this case BackupPC, query all the Hiera data for each node where the backup directories/databases are stored. Then use all that information on the BackupPC server to generate proper configuration files for each

Hi, I've a question about a FQDN VS Shorewall configuration: I'd like to install a firewall that should forward the web requests to different web servers (iis, apache, and so on...); all web sites are registered with the same ip to internic (eg. www.example1.com-->151.99.234.3-->apache-server, www.example2.com-- >151.99.234.3-->iis-server, etc...) so I'm wondering if I

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:

Package: logcheck Version: 1.3.7 Severity: normal After installing logcheck on a system it posted an error to the cron mail address hourly. An untrapped script error was posting stderr output to cron. It originated here: # Hostname either fully qualified or not. if [ $FQDN -eq 1 ]; then HOSTNAME="$(hostname --fqdn)" > /dev/null 2>&1 else

Hi there, We have a fake environment in which we test software and config before rolling it out to prod. Here, we have a fake puppetmasterd running, serving the new config under test. But we''re having trouble with certificates. It is possible to specify via config what fqdn the puppet ca should use for itself? We need this to be a different (faked) fqdn than the real name of the

Ok, on the subject, shares not acceccable when using fqdn. The server must have a A and PTR record for the real hostname within the REALM, then any CNAME should work. But if the Primary domain or the search domain is incorrect ( on the client) then, \\FQDN(CNAME)\share wont work, since it cannot find the "real" hostname Which resolve to A/PTR. I did ask for an IPCONFIG /all from

Package: logcheck Version: 1.2.43a Severity: wishlist The conf file currently says # Should the hostname of the generated mails be fully qualified? FQDN=1 I suggest rewording that to # Should the hostname in the subject of the generated mails be fully qualified? FQDN=1 The current wording led me to believe that the sender, and perhaps recipient (if otherwise unqualified) of the emails generated

Well, I have finally installed Samba 4.9 from Van Belle's repo, but still I cannot resolve FQDN's. Dňa 22. 1. 2019 o 15:02 Rowland Penny via samba napísal(a): > On Tue, 22 Jan 2019 14:51:02 +0100 > "Mgr. Peter Tuharsky via samba" <samba at lists.samba.org> wrote: > >> Rowland, thank You, but this removes only the NS record, but the >> faulty domain A