search for: nslookups

Hello, has anybody a hint for me, how I can use nslookup to get either IPv6 AAAA only or both A and AAAA entries when doing this: e.g. # nslookup www.example.com Thanks, Walter

I just transfered fsmo roles from one DC to my newer DC and all went well. Thank you Samba team!! Great documentation, BTW. My domain (basically) consists of one ADDC, one member server and two W10 clients and one W7 client. While setting up the newer DC had been running some nslookup on the DC's and decided to run nslookup on my member server and do not know if I have discovered and

I have a Centos server that is running BIND and has IPv6 global addresses. I have entered a number of AAAA records into this copy of BIND in a local view and zone (tld is htt). Over IPv4, I have no trouble with nslookup ('nslookup - 127.0.0.1' and 'nslookup - 192.168.128.55'). I get the AAAA records back. But if I try to use the IPv6 address of the system I get a time out.

On Tue, October 11, 2016 15:23, Richard Mann wrote: >> -----Original Message----- >> From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >> Behalf Of Walter H. >> Sent: Tuesday, October 11, 2016 9:05 AM >> To: centos at centos.org >> Subject: [CentOS] Hint for nslookup wanted ... >> >> Hello, >> >> has anybody a

On 11/10/16 15:23, Richard Mann wrote: > Did your google break? > > For just IPv6 > nslookup -type=AAAA www.example.com > > For all records > nslookup -type=any www.example.com This is bad advice, because in DNS, ANY != ALL If you query with qtype=any, and you ask a caching resolver, then it will return to you all the records that are in its cache at that time, which

Hello, I am trying to setup a samba4 AD dc in my network using smb-tool. Everything seems to work except DNS forwarding. If I query for the dc root at dc:~# nslookup dc.local.domain.it I get the correct answer: root at dc:~# nslookup dc Server:???????? aaa.bbb.ccc.ddd Address:??????? aaa.bbb.ccc.ddd#53 Name:?? dc.xxxx.yyyy.it Address: aaa.bbb.ccc.ddd but if I query for an external domain: root

Hai James, Thanks, thats exactly what we needed. I'll comment below. > -----Oorspronkelijk bericht----- > Van: James Atwell [mailto:james.atwell365 at gmail.com] > Verzonden: donderdag 13 augustus 2020 14:46 > Aan: samba at lists.samba.org > CC: L.P.H. van Belle > Onderwerp: Re: [Samba] Samba DNS fails when queried with > nslookup commands > > Hi Louis and

Hello all, I am trying to configure a subdomain DNS server on a Cent OS 5.1 - for my lab. Brief configuration: Lab machine ---> 192.168.17.2 (should respond to DNS queries from hosts in 192.168.16.0/20 network) 1. I would also like to forward any queries outside the above network to our corporate domain (no firewalls between our 192.168.16.x network and the corporate network. The domain

> -----Oorspronkelijk bericht----- > Van: James Atwell [mailto:james.atwell365 at gmail.com] > Verzonden: donderdag 13 augustus 2020 16:48 > Aan: samba at lists.samba.org > CC: L.P.H. van Belle > Onderwerp: Re: [Samba] Samba DNS fails when queried with > nslookup commands > > > On 8/13/2020 9:57 AM, L.P.H. van Belle via samba wrote: > > Hai James, > >

> -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of Walter H. > Sent: Tuesday, October 11, 2016 9:05 AM > To: centos at centos.org > Subject: [CentOS] Hint for nslookup wanted ... > > Hello, > > has anybody a hint for me, how I can use nslookup to get > either IPv6 AAAA only or both A and AAAA

On 2016-10-08 07:58, Rowland Penny via samba wrote: > On Sat, 08 Oct 2016 07:50:03 -0500 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> I have built a second dtdc03 and joined to my first dtdc01. Thought >> all was well but, discovered that reverse dns is not correct on second >> dtdc03. >> >> root at dtdc03:~# host dtdc03

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

Hai, Only the forwarder is running in this systemd setup. This : 127.0.0.53:53 does NOT conflict with normaly resolv.conf setting Because samba or any dns server does not run on 127.0.0.53 Dont make the mistake to see this for : 127.0.0.1 Please show : /etc/hosts /etc/resolv.conf Depending on which one your using: /etc/network/interfaces and/or /etc/netplan/01-netcfg.yaml

Yes, i believe you hitted "not" having the "root zone" in internal DNS. If i recall correctly its somewhere in 4.4. or 4.5 fix. But as Rowland said, i suggest also upgrading. ps other fix is, switch to bind9_DLZ But again i still advice to upgrade. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens

On 02/12/15 10:31, mj wrote: >> I can find on the internet multiple instances of 'every DC running dns >> should have a SOA record', but I cannot find any concrete examples of an >> ldif that shows this. Does each DC have a separate SOA record in AD, or >> is there just one SOA record and the DC just claims to be the SOA, or is >> there just one SOA record

Hello Kris, On 03/02/2020 07:15, Kris Lou via samba wrote: > Unless it's_not_ a global catalog. Check your SRV records again, there > should be corresponding "_gc" records (similar to "_ldap") for each DC. Checked and both DCs pass all tests:- host -t SRV _ldap._tcp.mydomain.com. host -t SRV _gc._tcp.mydomain.com. host -t SRV _kerberos._udp.mydomain.com. host -t

I have built a second dtdc03 and joined to my first dtdc01. Thought all was well but, discovered that reverse dns is not correct on second dtdc03. root at dtdc03:~# host dtdc03 dtdc03.dtshrm.dt has address 192.168.16.49 root at dtdc03:~# host 192.168.16.49 Host 49.16.168.192.in-addr.arpa. not found: 3(NXDOMAIN) root at dtdc03:~# nslookup dtdc03 Server: 192.168.16.49 Address: 192.168.16.49#53

That is because your resolving setup is wrong. You problem starts here. Checking file: /etc/resolv.conf search patrikx3.com search corifeus.com search p3x-dc.patrikx3.com The first 2 will do nothing, only last will be used that setup. You want : search p3x-dc.patrikx3.com patrikx3.com corifeus.com But still thats not needed, you only need. search p3x-dc.patrikx3.com Because the other

Hello everyone, I playing around with ENUM and have configured * to query a few sources for testing purposes (fierymoon, e164.arpa, e164.org). I'd like to know if there is a way to query these servers manually (ie outside of asterisk via nslookup or equivalent) to find out if particular exchanges are listed with wildcards, so as to terminate calls to those prefixes (I'm not trying to

I have done the bind config like Rowland's post. The problem is still the same. windows: nslookup foo -> nxdomain nslookup foo. -> ip of DC in linux both is return an ip Whats about the file named.conf.update in samba/private? I have try to include in named.conf or in dlz "AD DNS Zone"{ ... include ../named.conf.update } without success. My bind log errors like