Displaying 6 results from an estimated 6 matches for "intelhd".
2019 Feb 09
4
Samba + BIND9 DLZ. DNS dosen't resolve FQDN, only short hostname
...s=f0, serial=27, ttl=900)
Name=blacktux, Records=1, Children=0
A: 10.20.1.1 (flags=f0, serial=2, ttl=900)
Name=boss, Records=1, Children=0
A: 10.20.3.78 (flags=f0, serial=39, ttl=900)
Name=DomainDnsZones, Records=0, Children=2
Name=ForestDnsZones, Records=0, Children=2
Name=intelhd, Records=1, Children=0
A: 10.20.1.82 (flags=f0, serial=20, ttl=900)
Name=w7-virt, Records=1, Children=0
A: 10.10.10.102 (flags=f0, serial=21, ttl=900)
Dňa 8. 2. 2019 o 21:56 Rowland Penny via samba napísal(a):
> On Fri, 8 Feb 2019 21:19:20 +0100
> Peter Tuharsky via samba <sa...
2019 Feb 09
0
Samba + BIND9 DLZ. DNS dosen't resolve FQDN, only short hostname
...ame=blacktux, Records=1, Children=0
> A: 10.20.1.1 (flags=f0, serial=2, ttl=900)
> Name=boss, Records=1, Children=0
> A: 10.20.3.78 (flags=f0, serial=39, ttl=900)
> Name=DomainDnsZones, Records=0, Children=2
> Name=ForestDnsZones, Records=0, Children=2
> Name=intelhd, Records=1, Children=0
> A: 10.20.1.82 (flags=f0, serial=20, ttl=900)
> Name=w7-virt, Records=1, Children=0
> A: 10.10.10.102 (flags=f0, serial=21, ttl=900)
>
Hmm, mine look different:
If I run (on a DC):
samba-tool dns query 127.0.0.1 samdom.example.com @ SOA
I get:...
2019 Feb 08
2
Samba + BIND9 DLZ. DNS dosen't resolve FQDN, only short hostname
like this, Rowland:
samba-tool dns add -U administrator 10.20.1.1 interbronz.local
asus.interbronz.local A 10.20.4.69
Dňa 7. 2. 2019 o 21:24 Rowland Penny via samba napísal(a):
> On Thu, 7 Feb 2019 21:05:12 +0100
> Peter Tuharsky via samba <samba at lists.samba.org> wrote:
>
>> Well, I have finally installed Samba 4.9 from Van Belle's repo, but
>> still I cannot
2019 Feb 20
2
Samba + BIND9 DLZ. DNS dosen't resolve FQDN, only short hostname
...Children=0
>> A: 10.20.1.1 (flags=f0, serial=2, ttl=900)
>> Name=boss, Records=1, Children=0
>> A: 10.20.3.78 (flags=f0, serial=39, ttl=900)
>> Name=DomainDnsZones, Records=0, Children=2
>> Name=ForestDnsZones, Records=0, Children=2
>> Name=intelhd, Records=1, Children=0
>> A: 10.20.1.82 (flags=f0, serial=20, ttl=900)
>> Name=w7-virt, Records=1, Children=0
>> A: 10.10.10.102 (flags=f0, serial=21, ttl=900)
>>
>
> Hmm, mine look different:
>
> If I run (on a DC):
>
> samba-tool dns query 12...
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
2019 Jan 12
2
Samba + BIND9 DLZ. DNS dosen't resolve FQDN, only short hostname
...rial=1, ttl=900)
A: 10.20.1.1 (flags=f0, serial=2, ttl=900)
A: 10.30.1.1 (flags=f0, serial=22, ttl=900)
Name=boss, Records=1, Children=0
A: 10.20.3.78 (flags=f0, serial=18, ttl=900)
Name=DomainDnsZones, Records=0, Children=2
Name=ForestDnsZones, Records=0, Children=2
Name=intelhd, Records=1, Children=0
A: 10.20.1.82 (flags=f0, serial=20, ttl=900)
Name=w7-virt, Records=1, Children=0
A: 10.10.10.102 (flags=f0, serial=21, ttl=900)
The question is, whether Samba even knows how to, or should it ever,
resolve FQDNs.
I see there are more NS records for server itse...