search for: nslookup

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 possible problem or not. On the member server, running nslookup returns: root at dtmbr01:~# nslookup dtmbr01 Server: 192.168.16.49 Address: 192.168.16.49#53 Name: dtmbr01.dtshr...

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. Both from nslookup and from ping6. I setup /etc/resolv.conf as shown at: http://docsun.cites.uiuc.edu/sun_docs/C/solaris...

...016 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 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 >> > > Did your google break? no...

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 may or may...

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 at dc:~# nslookup www.nasa.gov Server:???????? aaa.bbb.ccc.ddd Add...

...;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 Rowland, > > ?????? Thanks for the help. Below is the information > requested before I change anything. > > nameserver 172.16.23.30 > nameserver 172.16.23.28 > nameserver 127.0.0.53 < or on top or remove.. Now its never used. Best....

...e DNS/Bind records were based upon the auto-generated files from the Bind GUI Config tool. 3. I also changed myhost's resolv.conf to reflect the following: search lab.mycompany.com 192.168.17.2 search mycompany.com 10.100.1.2 ====== PROBLEM: 1. When I am in myhost.com, I can perform: a. nslookup hostname (to any host within 192.168.x and 10.100.x networks) b. nslookup ip to anyhost wtihin both networks. 2. When I am in one of the hosts within 192.168.x aside from myhost.com (for example, qaserver1 or qaserver2): a: SUCCESS to nslookup hostname to any host within BOTH networks. b. FAIL...

> -----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, > > > > Thanks, thats exactly what we needed. > > I'll comment below. > > > > > > ** SNIP ** > > > Louis, > > ????? Couldn't figure o...

> -----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 entries when doing this: > > e.g. > > # nslookup www.example.com > Did your google break? For just IPv6 nslookup -type=AAAA www.exampl...

...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 >> >> Name: dtdc03.dtshrm.dt >> Address: 192.168.16.49 >> >> root at dtdc03:~# nslookup 192.168.16.49 >> Server: 192.168.16.49 >> Address: 192.168.16.49#53 >> >> ** s...

...ask[dn udp??????? 0????? 0 127.0.0.53:53 0.0.0.0:*?????????????????????????? 2935/systemd-resolv udp6?????? 0????? 0 :::53 :::*??????????????????????????????? 2694/samba: task[dn How do I disable systemd-resolve and ensure only samba is listening on port 53 for DNS requests?? You can see below nslookup succeeds when querying another server in the network but fails on this one. root at soldc4:~# nslookup google.com soldc1 Server:???????? soldc1 Address:??????? 172.16.23.28#53 Non-authoritative answer: Name:?? google.com Address: 172.217.7.238 Name:?? google.com Address: 2607:f8b0:4004:806::200e...

...etz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland penny via samba > Verzonden: donderdag 13 augustus 2020 8:19 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Samba DNS fails when queried with > nslookup commands > > On 12/08/2020 21:49, James Atwell via samba wrote: > > 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 po...

...Onderwerp: Re: [Samba] internal DNS not forwarding > > Hi Louis, > > root at dc:~# samba -V > Version 4.3.11-Ubuntu > > Andrea > > Il 14/07/20 13:55, L.P.H. van Belle via samba ha scritto: > > Yes, all these work here also (! With bind9_dlz ) > > > > nslookup nasa.org $(hostname -i) ( running the command on > the DC itself.) > > nslookup nasa.org 1.1.1.1 > > nslookup nasa.org 8.8.8.8 > > > > Old samba version without the root zone provisioned maybe? > > That is an old bug. > > > > Which samba version is this...

...eed for it to actually be in the database (so it > would perhaps not show up in an ldif) > > MJ > This is what I think happens and if this is the case, then samba itself will have to do this, but I have added an NS record for the 2nd DC to the SOA record with samba-tool and if I use nslookup I get this: nslookup > set querytype=soa > samdom.example.com Server: 192.168.0.5 Address: 192.168.0.5#53 samdom.example.com origin = dc1.samdom.example.com mail addr = hostmaster.samdom.example.com serial = 101 refresh = 900 retry = 600 expire = 86...

...based upon the link/graphic I posted earlier: > * either your 2nd DC isn't being returned as a part of DNS lookups For the Windows desktops and the QNAP server, they have the IP addresses for both DCs in their respective DNS settings. For a Windows desktop tested this morning, the command nslookup defaults to DC3 at 192.168.0.218 but when that was "down" DNS queries timed out. > * or that 2nd DC isn't responding to queries for authentication Both DCs have this as their Kerberos configuration (/etc/krb5.conf):- [libdefaults] default_realm = MYDOMAIN.COM...

...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 Name: dtdc03.dtshrm.dt Address: 192.168.16.49 root at dtdc03:~# nslookup 192.168.16.49 Server: 192.168.16.49 Address: 192.168.16.49#53 ** server can't find 49.16.168.192.in-addr.arpa: NXDOMAIN I tried to add the reverse zone (I may...

...good advice here. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Patrik via samba > Verzonden: maandag 5 augustus 2019 13:38 > Aan: Rowland penny > CC: sambalist > Onderwerp: Re: [Samba] samba dlz. bind9 nslookup is wrong > > the problem is that here: > root at server:~# nslookup p3x-dc.patrikx3.com > Server: 192.168.78.20 > Address: 192.168.78.20#53 > > Name: p3x-dc.patrikx3.com > Address: 192.168.78.20 > Name: p3x-dc.patrikx3.com > *Address: 192.168.81.120* > Name: p3x-d...

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 query for specific end-user telephone numbers). I've seen the syntax of the NAPTR records indicating that an '*' represents the wildcard but I...

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 named[27869]...