Displaying 20 results from an estimated 90000 matches similar to: "problem with dns"
2019 Jan 11
2
Samba + BIND9 DLZ. DNS dosen't resolve FQDN, only short hostname
> >
> > 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
2008 Oct 22
3
i would like to add asterix to my centos
I want to add a server of VoIP under my server, but I don't have de doawnload and i don't have the tutotrial. please help me
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos/attachments/20081022/47da91cd/attachment-0003.html>
2008 Oct 13
1
problem with roundcubemail
?I use the webmail roundcubemail to edit my mail server. after finishing to configure it and mysql server and I try? to connect ?to the mail server but i had this message :? ?unable to connect to the database.? help me please?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2024 Jun 10
1
Fwd: Two DNS issues with samba
On Sun, 9 Jun 2024 13:18:10 +0200
Ronny Preiss via samba <samba at lists.samba.org> wrote:
> > No need to build Samba yourself, you can find packages here:
> >
> > http://www.corpit.ru/mjt/packages/samba/
> How can I install these files?
Try reading the 'README' file from the link I posted.
>
> Here are the requested files from both servers.
>
>
2015 Mar 12
2
samba 4.1.17 on raspberry pi as ad dc - internal dns problems
Hello List,
I have a raspberry pi with raspbian. I am trying to get samba 4.1.17 to
work as AD DC and have problems which seem to be dns related...
What I did to get here:
- I removed the preinstalled samba
- installed prerequisites (build-essential libacl1-dev libattr1-dev
libblkid-dev libgnutls-dev libreadline-dev python-dev libpam0g-dev
python-dnspython gdb pkg-config libpopt-dev
2008 Dec 29
4
DNS resolver over IPv6
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.
2016 May 15
2
DC2: TKEY is unacceptable, Failed DNS update?
I installed
two virtual machines with Samba as domain controllers for the same domain. I
was struggling with network and DNS configuration initially, maybe my problem
is related.
DC1 starts
up ok, the last line of the log reads
STATUS=daemon
'samba' finished starting up and ready to serve connections
DC2 starts
with plenty of lines
[2016/05/15 22:00:32.744910, 0]
2015 Mar 12
5
samba 4.1.17 on raspberry pi as ad dc - internal dns problems
Hey Peter,
many thanks for your reply.
---
regarding .local domains
I know this is regarded by some as bad form, is actively being
discouraged by the samba wiki and can cause problems with
bonjour/zerobla configuration.
I can say for certain that no apple devices will ever come anywhere near
that network and the other drawbacks of .local like getting signed
certs... should never be an issue
2019 Jan 12
2
Samba + BIND9 DLZ. DNS dosen't resolve FQDN, only short hostname
Thank You, Luis, Rowland,
for the initial hints. I checked them all.
As of system, it is Debian Strech, Bind 9.10.3, Samba 4.5.12 (I know it
is old, but is native for distribution, and should work in such simple
setup I suppose). I used this howto:
https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller
As of hosts.conf, there are only localhost and
2017 May 11
1
Upgrading BIND DNS Backend
Hello Marc,
Upgrade DNS worked properly as you can see below.
---------
samba_upgradedns --dns-backend=BIND9_DLZ
Reading domain information
DNS accounts already exist
No zone file /usr/local/samba/private/dns/EXZA.LOCAL.zone
# is this the culprit?
DNS records will be automatically created
DNS partitions already exist
dns-dc account already exists
See
2020 May 15
5
DNS problem ubuntu server 20.04
> -----Oorspronkelijk bericht-----
> Van: samba-technical
> [mailto:samba-technical-bounces at lists.samba.org] Namens
> Rowland penny via samba-technical
> Verzonden: donderdag 14 mei 2020 21:20
> Aan: samba-technical at lists.samba.org
> Onderwerp: Re: DNS problem ubuntu server 20.04
>
> On 14/05/2020 18:57, RickJC1 via samba-technical wrote:
> > Hello
2016 Jun 30
2
DNS Suddenly breaking
Yes, it's set up with 8.8.8.8
I'm able to ping it without issues, jut not able to resolve anything
externally.
On Thu, Jun 30, 2016 at 9:09 AM, mathias dufresne <infractory at gmail.com>
wrote:
> To get recursion working with internal DNS you only need to set up:
> dns forwarder = <IP of your main DNS>
>
> Is it configured?
>
> If yes and packets can go
2017 May 16
2
DNS (bind_dlz) forwarding not working
Hello,
I provisioned an samba AD with the bind_dlz option. So far so
good. Followed the samba wiki.
I have a DNS for our external access services (website, moodle, etc) and
I'm using it as a forwarder to AD but it is not working.
In a win7 I configured the AD IP as primary DNS and put it in the domain.
When I try to access, for example, "wiki.samba.org" it opens normally, but
when
2020 Apr 12
2
BIND9/DNS lookups stopped working after upgrading our Comcast modem/gateway
OK here's our setup, we're running pfSense as our firewall/router. We
have a dual-WAN with a Comcast Business Gateway and another local ISP.
We're running Samba 4.7.6 as the AD DC & Bind 9.9.4. Here's the issue,
we just upgraded our Comcast service to a higher speed & they replaced
the modem/gateway. Everything was working fine, before the modem swap.
Once they did
2024 Jun 09
1
Fwd: Two DNS issues with samba
> No need to build Samba yourself, you can find packages here:
>
> http://www.corpit.ru/mjt/packages/samba/
How can I install these files?
Here are the requested files from both servers.
## DC01 ##
/etc/hostname
01-dc01
-----
/etc/hosts
127.0.0.1 localhost
#127.0.1.1 01-dc01
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0
2005 Jun 23
3
Automated YUM update kills DNS
We've got several CentOS 3.x systems running DNS that we keep updated
automatically via YUM.
Recently two of those systems (not all of them) when updating themselves
to the latest versions of BIND, automatically replaced /etc/named.conf
with a new one and saved the old one as /etc/named.conf.rpmsave.
Which of course broke DNS for those servers.
All servers got updated, but only two of
2005 Jan 22
5
EROR: no DNS
[2005-01-22 23:31:17] EROR yp/send_to_yp connection to http://dir.xiph.org/cgi-bin/yp-cgi failed with "Couldn't resolve host 'dir.xiph.org'"
[2005-01-22 23:31:17] EROR yp/send_to_yp connection to http://www.oddsock.org/cgi-bin/yp-cgi failed with "Couldn't resolve host 'www.oddsock.org'"
This happens in chroot. Out of chroot, no problems. So I did the
2020 Feb 17
2
Internal DNS, update of reverse zone fails
On 17/02/2020 10:24, Rowland penny via samba wrote:
> On 17/02/2020 08:42, kaffeesurrogat wrote:
>> Dear Rowland,
>>
>> Yes, I did. I'm reading a lot. Docs, books, ... Updates of the
>> dns-server via DHCP is up and running, both for the reverse lookup zone
>> and the forward lookup mechanism. I've set the lease time to a very low
>> value to make
2015 Mar 19
3
Fwd: Dynamic DNS Updates not working. samba_dnsupdate : (sambalist: message 3 of 20) RuntimeError: (sambalist: to exclusive) kinit for [DC@Realm] failed (Cannot contact any KDC for requested realm)
Timo Altun schrieb am 19.03.2015 10:30:
> As I wrote in my first mail, Kerberos does work. I can successfully request
> and list a ticket on the AC DC.
OK, then next things, which come to my mind are:
is the keytab, you set in named.conf.options readable
for the user, under which bind is run.
Then, is the /etc/bind/namedb writable for bind.
And in the end, it might be a screwed up
2016 Jun 30
2
DNS Suddenly breaking
Hosts:
127.0.0.1 localhost localhost.localdomain localhost4
localhost4.localdomain4
::1 localhost localhost.localdomain localhost6
localhost6.localdomain6
192.168.1.235 bus-ny-dc-01.domain.domain.com bus-ny-dc-01
Resolv:
# Generated by NetworkManager
search domain.domain.com
nameserver 192.168.1.236
nameserver 192.168.1.235
Smb.conf:
# Global parameters
[global]
workgroup =