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?
On 29/06/15 18:44, 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?OK, can you ping 'ftp3.nrc.ca' from a workstation ? Does it work from the AD DC ? How are the workstations getting their DNS info, if it is DHCP, are they getting full and correct info? Rowland
can you ping 8.8.8.8 from the affected host? On 6/29/2015 19:44, 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?
On 29/06/15 02:12 PM, mourik jan heupink wrote:> can you ping 8.8.8.8 from the affected host? >Not a problem. The pings take about 25ms.
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.
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. >
Maybe Matching Threads
- resolve errors with Samba 4 dns [RESOLVED]
- GlusterFS 3.8 Debian 8 apt repository broken
- GlusterFS 3.8 Debian 8 apt repository broken
- GlusterFS 3.8 Debian 8 apt repository broken
- Issues starting RStudio Server and release file expiration under Debian (Jessie)