Your message dated Sat, 8 Sep 2018 00:05:51 +0200
with message-id <[email protected]>
and subject line Closing old bugs
has caused the Debian Bug report #795598,
regarding ntpdate can't resolve DNS names
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
795598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795598
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ntpdate
Version: 1:4.2.6.p5+dfsg-7

Hello,

/etc/resolv.conf:
nameserver 192.168.0.1
search localnet

I also have ppp 2.4.6-3.1 with usepeerdns disabled in order not to overwrite 
/etc/resolv.conf above.

When pppd makes a PPPoE connection to my ISP on bootup and invokes 
/etc/network/if-up.d/ntpdate (among other scripts),
it cannot resolve DNS names listed in /etc/openntpd/ntpd.conf:
Aug 15 19:46:37 rihad ntpdate[942]: Can't find host 0.debian.pool.ntp.org: Name 
or service not known (-2)
Aug 15 19:46:37 rihad ntpdate[942]: Can't find host 1.debian.pool.ntp.org: Name 
or service not known (-2)
Aug 15 19:46:37 rihad ntpdate[942]: Can't find host 2.debian.pool.ntp.org: Name 
or service not known (-2)
Aug 15 19:46:37 rihad ntpdate[942]: Can't find host 3.debian.pool.ntp.org: Name 
or service not known (-2)
Aug 15 19:46:37 rihad ntpdate[942]: no servers can be used, exiting

Most likely because bind9 starts up AFTER it.

I am using Debian GNU/Linux 8.1, kernel 3.16.0-4-amd64 #1 SMP Debian 
3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux
and libc6:amd64 2.19-18

--- End Message ---
--- Begin Message ---
Hello,

thank you for spending your time helping to make Debian better with
this bug report. Unfortunately your bug report could not be (completely)
dealt with in an appropriate time.

The version you have filed this bug report against is for a release that
is not supported anymore. Unfortunately we do not have the manpower to
reproduce bugs that old. It is possibly already fixed with the current
version.

Therefor I'm closing this bug. If you can still reproduce this issue on
a supported release (Debian 9 aka stretch, preferably also in sid) feel
free to reopen the bug report.

Thanks,
Bernhard

--- End Message ---

Reply via email to