On 23-5-2016 8:45, li...@wrant.com wrote: >>>>>>> For some reasons, i notice that i am not able to access some website in >>>>>>> the first 10 minutes when i have my machine turned on. >>>>>> >>>>>> If you have a broadband on premises equipment like a converter, modem, >>>>>> router, switch etc, you may consider replacing these, as with age some >>>>>> of them degrade (in capacitors, solder joints, jacks) and such devices >>>>>> have trouble working reliably until it warms up (or when they overheat). >>>>>> >>>>>> To report further details to the list, please start a new empty message. >>>>>> >>>>> >>>>> Well,the modem hardware is new. >>>>> my switches are ok, i have a local server that is up for 24/7, en even >>>>> that machine is loosing contact to the website. >>>> >>>> So you're absolutely sure the hardware environment is fine. There are >>>> two important tactics to employ then in troubleshooting. First one is >>>> to bypass every equipment and connect the troubleshooting device direct >>>> to the upstream connection. Then ensure you have full connectivity and >>>> move down the line to the point you find your issue. You would follow >>>> this with the second tactic, drop the configuration from zero and make >>>> sure you have working connectivity and then start adding each piece of >>>> the software set up, until you find the part that generates the issues. >>>> >>>>> it is pure a dns isue, but what i can resolv, i rewrote the complete >>>>> named stuff, added even the DNS server pool from that website, heck, >>>>> still no result... >>>> >>>> Try unbound / nsd and see if this gives you a different result. It is >>>> often just such a simple common issue, that it's hidden in plain sight. >>>> >>>> Once you have found it, please report to the list your process+results. >>> >>> This gonna be fun for me. >>> But i will do it. >> >> I know very well what you mean. Then, if you want to cut time short, >> you can preemptively start looking direct into the suspected trouble >> zone, either hardware, equipment configuration and/or software set up. >> >> With this second approach, you can ask a direct question once you find >> the point of hesitation and/or concern. Just walking the trouble path >> is often enough to get you out of the "unseeing" mode and find it quick. > > One more important thing, if you are using the ISP provided name servers > or name service from the broadband equipment (duh), you can bypass these > and use own local direct resolving recursive name server on your gateway. >
as say's. took again a look at my config's And made these changes. dhcpd.conf. Added 2nd nameserver option domain-name-servers 192.168.0.240, 192.168.1.240; was option domain-name-servers 192.168.0.240; dont ask me why, but this did the trick for most websited. resolv.conf WAS ## resolv.conf ## # Generated by re0 dhclient search xs4non.nl nameserver 192.168.0.240 nameserver 192.168.1.240 nameserver 8.8.8.8 nameserver 8.8.4.4 lookup file bind is now. # Generated by re0 dhclient domain xs4non.nl nameserver 127.0.0.1 nameserver 8.8.8.8 nameserver 8.8.4.4 fixed most of the rest of borked websites, ex 1. that still gives some ping isues. but i looked this morning in my modem, i readed somewhere the thing should get new firmware, and surpricingly it had a option in the dns section where i can add 8 more dns servers. so i added there als the google dns (unless some1 has beter adresses) now its, waiting time and i revamped named.conf personaly i think i have a isue in it. but,. i am still doing the error tree search.. Tony.
