Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #190320 > unrolled thread

BIND DNS problem after upgrading from Wheezy to Squeeze

Back to article view | Back to linux.debian.user

Contents

  BIND DNS problem after upgrading from Wheezy to Squeeze Andrew W <andrewjameswood@ymail.com> - 2017-12-26 18:40 +0100
    Re: BIND DNS problem after upgrading from Wheezy to Squeeze deloptes <deloptes@gmail.com> - 2017-12-26 19:10 +0100

#190320 — BIND DNS problem after upgrading from Wheezy to Squeeze

I have a server which acts as a DNS server for our LAN. All our internal 
servers have A records on it using a .local domain and it forwards all 
other requests out to the root servers using the in built list provided 
with BIND. All clients on the LAN have this machine set as their only 
DNS server.


It has worked fine for 6 years under Wheezy but I have just upgraded it 
to Stretch. I did an upgrade to Jessie first, rebooted checked 
everything was OK, and then immediately upgraded to Stretch.

Since then we keep getting intermittent DNS lookup failures for various 
domains on the internet, which will typically work if you click the 
refresh button in the browser a few times.

BIND seems to just log to syslog/systemd it doesnt appear to be 
configured to use its own log. If I run journalctl -xe | grep "named" I 
can get the log entries but none of them relate to the failed DNS 
lookup. If I do it immediately after a failure has occured nothing is 
logged so Im at a bit of a loss to work out what might be wrong.


Does anyone have any ideas please?


Thanks

Andrew

PS I should add that as far as I can tell it has never had a problem 
with resolving our internal .local domain it just seems to be real 
internet domains its having issues with.

[toc] | [next] | [standalone]

#190323

Andrew W wrote:


> 
> 
> Does anyone have any ideas please?
> 

I had the same experience - I think (after trying this and that) the
solution was ntp (time was behind on the server), but I am not really 100%.
I was thinking first it has something to do with ipv6 or firewall, but after
updating the time, it disappeared.

perhaps it may help in your case to see if you sync up your machine time

regards

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web