mourik jan heupink
2015-Jun-29 19:00 UTC
[Samba] resolve errors with Samba 4 dns [RESOLVED]
and 'host google.com 8.8.8.8' also gives the expected output? Like this:> root at pf:~# host google.com 8.8.8.8 > Using domain server: > Name: 8.8.8.8 > Address: 8.8.8.8#53 > Aliases: > > google.com has address 74.125.136.100 > google.com has address 74.125.136.113 > google.com has address 74.125.136.101 > google.com has address 74.125.136.138 > google.com has address 74.125.136.102 > google.com has address 74.125.136.139 > google.com has IPv6 address 2a00:1450:4013:c01::71 > google.com mail is handled by 50 alt4.aspmx.l.google.com. > google.com mail is handled by 10 aspmx.l.google.com. > google.com mail is handled by 30 alt2.aspmx.l.google.com. > google.com mail is handled by 20 alt1.aspmx.l.google.com. > google.com mail is handled by 40 alt3.aspmx.l.google.com. > root at pf:~#How many dns servers are there in your /etc/resolv.conf? If the google one works (like above) then I'd try with only dns server: the google dns. On 6/29/2015 20:41, Gary Dale wrote:> On 29/06/15 01:44 PM, Gary Dale wrote: >> I'm running Debian/Jessie on a server which is used as an AD DC. I'm >> getting errors like this: >> >> Hit http://ftp.ca.debian.org jessie InRelease >> Hit http://ftp.ca.debian.org jessie/main Sources >> Hit http://ftp.ca.debian.org jessie/main amd64 Packages >> Hit http://ftp.ca.debian.org jessie/main Translation-en >> Err http://ftp3.nrc.ca jessie InRelease >> Err http://ftp3.nrc.ca jessie-updates InRelease >> Err http://security.debian.org jessie/updates InRelease >> Err http://security.debian.org jessie/updates Release.gpg >> Could not resolve 'security.debian.org' >> Err http://ftp3.nrc.ca jessie Release.gpg >> Could not resolve 'ftp3.nrc.ca' >> Err http://ftp3.nrc.ca jessie-updates Release.gpg >> Could not resolve 'ftp3.nrc.ca' >> W: Failed to fetch http://ftp3.nrc.ca/debian/dists/jessie/InRelease: >> W: Failed to fetch >> http://security.debian.org/dists/jessie/updates/InRelease: >> W: Failed to fetch >> http://ftp3.nrc.ca/debian/dists/jessie-updates/InRelease: >> W: Failed to fetch http://ftp3.nrc.ca/debian/dists/jessie/Release.gpg: >> Could not resolve 'ftp3.nrc.ca' >> W: Failed to fetch >> http://ftp3.nrc.ca/debian/dists/jessie-updates/Release.gpg: Could not >> resolve 'ftp3.nrc.ca' >> W: Failed to fetch >> http://security.debian.org/dists/jessie/updates/Release.gpg: Could not >> resolve 'security.debian.org' >> W: Some index files failed to download. They have been ignored, or old >> ones used instead. >> >> since installing Samba 4 and using its DNS server. I've tried >> forwarding to both my router, which has dns, and directly to Google's >> 8.8.8.8 DNS servers but the problems persist. >> >> On workstations, e-mail sometimes gets through and sometimes fails. >> Other Internet services are similarly iffy. >> >> Any suggestions? > > Found the problem - a loop between Samba's DNS server and the router. >
On 29/06/15 03:00 PM, mourik jan heupink wrote:> and 'host google.com 8.8.8.8' also gives the expected output? > > Like this: > >> root at pf:~# host google.com 8.8.8.8 >> Using domain server: >> Name: 8.8.8.8 >> Address: 8.8.8.8#53 >> Aliases: >> >> google.com has address 74.125.136.100 >> google.com has address 74.125.136.113 >> google.com has address 74.125.136.101 >> google.com has address 74.125.136.138 >> google.com has address 74.125.136.102 >> google.com has address 74.125.136.139 >> google.com has IPv6 address 2a00:1450:4013:c01::71 >> google.com mail is handled by 50 alt4.aspmx.l.google.com. >> google.com mail is handled by 10 aspmx.l.google.com. >> google.com mail is handled by 30 alt2.aspmx.l.google.com. >> google.com mail is handled by 20 alt1.aspmx.l.google.com. >> google.com mail is handled by 40 alt3.aspmx.l.google.com. >> root at pf:~# > > How many dns servers are there in your /etc/resolv.conf? If the google > one works (like above) then I'd try with only dns server: the google dns. >That wouldn't work. Google doesn't know about my LAN servers. The AD DC needs to be the first DNS server. After that, Google or OpenDNS can handle the public addresses.
On 29/06/15 03:00 PM, mourik jan heupink wrote:> and 'host google.com 8.8.8.8' also gives the expected output? > > Like this: > >> root at pf:~# host google.com 8.8.8.8 >> Using domain server: >> Name: 8.8.8.8 >> Address: 8.8.8.8#53 >> Aliases: >> >> google.com has address 74.125.136.100 >> google.com has address 74.125.136.113 >> google.com has address 74.125.136.101 >> google.com has address 74.125.136.138 >> google.com has address 74.125.136.102 >> google.com has address 74.125.136.139 >> google.com has IPv6 address 2a00:1450:4013:c01::71 >> google.com mail is handled by 50 alt4.aspmx.l.google.com. >> google.com mail is handled by 10 aspmx.l.google.com. >> google.com mail is handled by 30 alt2.aspmx.l.google.com. >> google.com mail is handled by 20 alt1.aspmx.l.google.com. >> google.com mail is handled by 40 alt3.aspmx.l.google.com. >> root at pf:~# > > How many dns servers are there in your /etc/resolv.conf? If the google > one works (like above) then I'd try with only dns server: the google dns.Actually, my current setup, which seems to be working, has my AD DC as the primary and Google second. I've also set my router to use OpenDNS. If someone comes with a new device, it gets its settings from the router's DHCP service. Conversely, I've set all the workstations with static IP addresses using the AD DC and Google.
mourik jan heupink
2015-Jun-30 11:17 UTC
[Samba] resolve errors with Samba 4 dns [RESOLVED]
> That wouldn't work. Google doesn't know about my LAN servers. The AD DC > needs to be the first DNS server. After that, Google or OpenDNS can > handle the public addresses.Well, your original problem/question was like:> Err http://ftp3.nrc.ca jessie-updates Release.gpg > Could not resolve 'ftp3.nrc.ca'Anyway, glad you got it solved.