similar to: Samba AD not resolving external names

Displaying 20 results from an estimated 1000 matches similar to: "Samba AD not resolving external names"

2020 Sep 05
3
Samba AD not resolving external names
I think it?s the cache. When you where sleeping the cache got updated. But I can be wrong Philip > On 5 Sep 2020, at 12:35, Rowland penny via samba <samba at lists.samba.org> wrote: > > On 05/09/2020 09:53, Peter Pollock via samba wrote: >> I have just set up a new AD and am having a little success with it, but DNS >> resolution is a little slow. >> >>
2020 Sep 05
1
Samba AD not resolving external names
I fell asleep at my desk... and now it's working fine. I have no idea what was wrong or why it magically fixed itself. On Sat, Sep 5, 2020 at 3:36 AM Rowland penny via samba < samba at lists.samba.org> wrote: > On 05/09/2020 09:53, Peter Pollock via samba wrote: > > I have just set up a new AD and am having a little success with it, but > DNS > > resolution is a
2020 Sep 05
0
Samba AD not resolving external names
After reboot, the problem came back again. Server refuses to resolve external names without "nameserver 8.8.8.8" in resolv.conf and gives the same SERVFAIL message when doing nslookup On Sat, Sep 5, 2020 at 9:02 AM Philip Offermans via samba < samba at lists.samba.org> wrote: > I think it?s the cache. When you where sleeping the cache got updated. But > I can be wrong
2020 Sep 06
2
Make new server the "master"
Thank you everyone for your help. I corrected my resolv.conf files as Peter Milesson suggested and then had to take a number of extra steps so now things are looking a little better. In case it helps anyone else in the future, here's what I found (plus I am now having problems resolving internal addresses). As far as I can see, the setup on both servers is identical (except they use their own
2020 Sep 05
2
Make new server the "master"
To get the question of why new servers, this one I'm using has hardware whose remaining life is measured in days. The elastic bands and sticky tape it is held together with won't hold for much longer. I'm using it to build and test a new environment, but then I need to migrate that onto something with a little more vitality before bringing it into production (in the next 56 hours). As
2020 Sep 03
3
Changing IP Scope on a Samba DC
On 03/09/2020 20:57, Peter Pollock wrote: > Ubuntu 20.4 and whatever Samba it installs (sorry, I'm not in front?of > the server right now). 4.11. x if I remember correctly, so okay to start with, but can I introduce to Louis Van Belle's repo: http://apt.van-belle.nl/ Once you get up and running, you can use the packages there to keep current. > > Bind 9.16 (although there
2020 Aug 12
7
Samba DNS fails when queried with nslookup commands
Hello, ???? Having issues with a DC not responding to DNS requests. OS is Ubuntu 18.04.4 LTS. Samba version 4.12.2 compiled from source. Checking to see what is listening on port 53 reports; @soldc4:~# netstat -tulpn | grep ":53" tcp??????? 0????? 0 127.0.0.53:53 0.0.0.0:*?????????????? LISTEN????? 2935/systemd-resolv tcp6?????? 0????? 0 :::53 :::*??????????????????? LISTEN?????
2012 Oct 16
3
setting up postfix
This should be an easy one. I'm trying to get postfix going. I've never done this before. I followed the directions at http://wiki.centos.org/HowTos/postfix. I opened port 25: iptables -I INPUT -p tcp -m tcp --dport 25 -j ACCEPT Here's an attempt to send mail: [motor at localhost motor]# mail -v larry.martell at gmail.com Subject: test test . EOT larry.martell at gmail.com...
2014 Oct 01
1
DHCP with ipv6 tunnel
I'm completely confused here and I'm hoping someone here has a setup they're willing to share, or help me configure things on my end. My connectivity is through Comcast, who unfortunately, does not offer ipv6 in my area. My connection goes like this: Comcast -> Motorola Surfboard Cable Router -> CentOS 6.5 server The CentOS server is multi-homed and manages the internal
2013 Mar 15
1
Postfix/Amavisd/Clamd - Mail send failing
Dear All With help from you all I am now at better stage. Special thanks to Robert. Atleast I am able to run all the required services (postfix, amavisd, clamd etc). I sent a mail from my gmail, I received at my newly setup domain/mailbox. I am facing issue while sending the mail outside. >From maillog I realized, two issues are there. *1. Virus scan failed. The error log is as below *
2005 Mar 26
1
Very slow wbinfo -u
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have set up Samba-3.0.11 to retrive account information from W2k server via winbind, and it works. But is takes about 10 sec. to retrive the information. I have dumped some traffic from the request, and it looks like this: A lot of these: 21:21:55.133423 172.20.3.131.1077 > 172.20.3.130.137: NBT UDP PACKET(137): QUERY; REQUEST; UNICAST
2014 Sep 05
1
Could not resolve host: mirror.centos.org
There seems to be a problem with my local dns server resolving mirror.centos.org. I know something about dns but obviously not enough to figure out what might be wrong here or how to fix this in bind configs. The SERVFAIL errors below seem to be related to AAAA and MX queries for the domain. Please advise. TIA. # host mirror.centos.org 8.8.8.8 Using domain server: Name: 8.8.8.8 Address:
2020 Sep 06
4
Make new server the "master"
Apparently I missed a step somewhere! On DC01 /etc/systemd/resolved.conf says [Resolve] #DNS= #FallbackDNS= #Domains= #LLMNR=no #MulticastDNS=no #DNSSEC=no #DNSOverTLS=no #Cache=yes #DNSStubListener=yes #ReadEtcHosts=yes On DC02 it reads [Resolve] DNS=8.8.8.8 FallbackDNS=8.8.4.4 #Domains= #LLMNR=no #MulticastDNS=no DNSSEC=no #DNSOverTLS=no #Cache=yes #DNSStubListener=yes #ReadEtcHosts=yes So
2007 Jun 13
1
SERVFAIL <=> NXDOMAIN
Hello, we encountered a problem with registry nic.at for tld .at and their transaction "BillWithDraw". This transaction allows an registrar to delegate authority back to registry. For a successful use of this transaction all nameserver-entries for the zone will be deleted by our application before nic-order will be sent to nic.at. Nic.at now checks all nameserver for existing
2020 Sep 05
5
Make new server the "master"
Please forgive me, I'm not sure what terminology to use here so this question may sound wrong. I have built two servers samba servers with a new domain. They replicate happily and I can seem to do everything I could ever want on them. DC01 holds all the FSMO roles and, as the first one built, acts as the "master" for DNS. Nothing works well on either server if DC01 is not at the
2007 Dec 15
2
DNS broken for www.voip-info.org ??
The DNS for www.voip-info.org seems to be non-responsive. Is there a mirror of this invaluable resource site? Tx, Steve dig www.voip-info.org ;; Got SERVFAIL reply from xxx.xxx.xxx.xxx, trying next server ; <<>> DiG 9.4.1-P1 <<>> www.voip-info.org ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 61402 ;;
2020 Sep 06
0
Make new server the "master"
On 06/09/2020 19:58, Peter Pollock wrote: > Thank you everyone for your help. I corrected my resolv.conf files as > Peter Milesson suggested and then had to take a number of extra steps > so now things are looking a little better. In case it helps anyone > else in the future, here's what I found (plus I am now having problems > resolving internal addresses). > > As far
2006 Sep 26
2
DNS help: "unexpected rcode (SERVFAIL)"??
Recently I'm getting these errors on my slave when adding new domains: Sep 26 13:48:27 hosting named[1668]: zone wholesaletvtime.com/IN: refresh: unexpected rcode (SERVFAIL) from master 207.218.174.4#53 The master/slave transfers work for the other 1000+ domains that I have, just not the handful of new ones that I just added after the CentOS 4.3 -> 4.4 upgrade. I regenerated the
2020 Nov 04
3
Samba shares with Windows ACL's
> > > > OK, you are using the winbind 'rid' backend, so it is okay to use > 'Domain Admins', so start again and follow that wikipage: > > Ensure you have the 'acl' & 'attr' packages installed (this is what they > are called on Debian based distros) > They are installed. I built the server using the walk through you gave me. >
2012 Nov 28
1
strange error
Hello, I have dns zone domain.com configured on nsd server. If a try #dig axfr @localhost domain.com then i receive correct answer, but if i try #dig a @localhost domain.com then i received nothing but should be 127.0.0.1 How can i troubleshoot this problem? output: [root at ns1 ~]# dig axfr @localhost domain.com ; <<>> DiG 9.8.3-P1-RedHat-9.8.3-2.P1.fc15 <<>> axfr