=== paride4 is now known as paride | ||
=== ivo_cavalcante is now known as IvoCavalcante | ||
=== IvoCavalcante is now known as Dante | ||
=== Dante is now known as Dantinho | ||
=== Dantinho is now known as ivo_cavalcante | ||
=== ivo_cavalcante is now known as IvoCavalcante | ||
=== IvoCavalcante is now known as ivo_cavalcante | ||
=== ivo_cavalcante is now known as IvoCavalcante | ||
=== IvoCavalcante is now known as ivo_cavalcante | ||
=== IvoCavalcante is now known as ivo_cavalcante | ||
=== ivo_cavalcante is now known as Dantinho | ||
=== Dantinho is now known as IvoCavalcante | ||
=== calcmandan_ is now known as calcmandan | ||
bigpod | can anyone help me i have a bind9 dns server on ubuntu with some internal dns stuff and a forwarder to a public DNS and sometimes my ubuntu just doesnt take the internal stuff wouldnt work | 16:07 |
---|---|---|
bigpod | but after i restart my laptop with ubuntu it can querry the internal stuff for a while | 16:07 |
Walex2 | bigpod: this comes up occasionally. Check the contents of 'resolv.conf' and the option 'rotate' or the equivalent for 'systemd-resolved'. | 18:07 |
Walex2 | bigpod: also run 'host' or 'nslookup' using the explicit server IP address. | 18:08 |
leftyfb | bigpod: pretty sure I told you this the other day. You need your client ONLY pointing to your local nameserver. Remove any public nameservers. Client DNS is not a failover system | 18:35 |
leftyfb | bigpod: to check which nameserver(s) your client is configured for: systemd-resolved --status |grep "DNS Servers" | 18:39 |
leftyfb | bigpod: you should only see your local bind server ip address as a result. Anything else should be removed either by the manual config on your client or on your DHCP server/router that assigns it via DHCP | 18:40 |
bigpod | leftyfb no i didnt talk to you about that besides i only have 1 server setup on clients | 19:02 |
bigpod | leftyfb: you and me were talking in ubuntu channel with someone else about this and were telling this to someone else | 19:03 |
bigpod | leftyfb: and just for future reference command is systemd-resolve not systemd-resolved | 19:04 |
leftyfb | bigpod: ok, are you at a point where the local resolutions are failing? | 19:06 |
bigpod | leftyfb: currently its working since i rebooted not long ago | 19:07 |
leftyfb | bigpod: ok, let us know when the problem resurfaces | 19:08 |
bigpod | yea and i think i might have figured out why it happened thanks to actualy your command and what Walex2 said, for some reason ipv6 dns setting reset on my laptop for some reason so i has had a ipv6 dns which used to be set to same server for ipv6 | 19:11 |
bigpod | leftyfb: so currently i guess im blaming that and thanks for the help and time and i hope that is it | 19:12 |
leftyfb | bigpod: personally I bitbucket ipv6 wherever possible. 20+ years and we still don't have it all figured out to the point it "just works" | 19:13 |
bigpod | leftyfb: well in past ipv6 dns used to give me trouble in past specialy on some other OSes so i should have first been like maybe its that right away | 19:16 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!